Jump to content

Unhandled Error and Paint.NET must close ,...


Majek

Recommended Posts

Crash log for Paint.NET v2.6 (Release Candidate 2 Release build 2.6.2232.23935)

Time of crash: 13.2.2006 11:43:49

OS version: 5.1.2600.131072 Service Pack 2 Workstation x86

.NET Framework version: 2.0.50727.42 x86

Processor count: 1

Physical memory: 511 MB

Exception details:

System.NullReferenceException: Object reference not set to an instance of an object.

at System.Windows.Forms.ToolStripSystemRenderer.RenderStatusStripBackground(ToolStripRenderEventArgs e)

at System.Windows.Forms.ToolStripSystemRenderer.OnRenderToolStripBackground(ToolStripRenderEventArgs e)

at System.Windows.Forms.ToolStripRenderer.DrawToolStripBackground(ToolStripRenderEventArgs e)

at System.Windows.Forms.ToolStrip.OnPaintBackground(PaintEventArgs e)

at System.Windows.Forms.StatusStrip.OnPaintBackground(PaintEventArgs e)

at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs)

at System.Windows.Forms.Control.WmPaint(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

at System.Windows.Forms.ToolStrip.WndProc(Message& m)

at System.Windows.Forms.StatusStrip.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

------------------------------------------------------------------------------

I must be very unlucky as it was the same with the previosu RC. So can anyone help me figure out what's wrng with my computer that i can't even run Paint? :cry:

Link to comment
Share on other sites

  • 2 weeks later...

I get the exact same error & the exact same pdncrash.log. I don't get it--I.ve had the .NET framework installed on my machine for months, and everything is patched & fully updated (XP Pro, SP2). Oh well, the GIMP works just fine for me, I'm not going to re-format my machine (as has been suggested to me by anothyer reviewer on File Forum) just to install this.

Link to comment
Share on other sites

try using the final version and check if it still errors

I have tried the final version as well as one of the RC's. Ahh, the joys of freeware!! I wish this project luck; maybe one day I'll even be able to use this!

EDIT: I've also tried the advice given by Rick Brewster here--http://paintdotnet.12.forumer.com ... ght=spooky

I ran the Windows Installer Cleanup utility, but there ar eno references to Paint.Net listed. I have uninstalled & reinstalled several times now; cleaning the registry after each uninstall, and I still get the same error & log...

Link to comment
Share on other sites

Here's a SS showing my desktop right after I try to run Paint.net v2.6 from my start menu (click on the thumbnail for a larger ss)---

paintneterrorss4br.th.jpg

Here are the entire contents of the crash log that was generated---

Crash log for Paint.NET v2.6 (Final Release build 2.6.2244.18680)

Time of crash: 2/26/2006 9:51:58 PM

OS version: 5.1.2600.131072 Service Pack 2 Workstation x86

.NET Framework version: 2.0.50727.42 x86

Processor count: 1

Physical memory: 2047 MB

Exception details:

System.NullReferenceException: Object reference not set to an instance of an object.

at System.Windows.Forms.ToolStripSystemRenderer.RenderStatusStripBackground(ToolStripRenderEventArgs e)

at System.Windows.Forms.ToolStripSystemRenderer.OnRenderToolStripBackground(ToolStripRenderEventArgs e)

at System.Windows.Forms.ToolStripRenderer.DrawToolStripBackground(ToolStripRenderEventArgs e)

at System.Windows.Forms.ToolStrip.OnPaintBackground(PaintEventArgs e)

at System.Windows.Forms.StatusStrip.OnPaintBackground(PaintEventArgs e)

at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs)

at System.Windows.Forms.Control.WmPaint(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

at System.Windows.Forms.ToolStrip.WndProc(Message& m)

at System.Windows.Forms.StatusStrip.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Link to comment
Share on other sites

That's exactly what I was looking for.

On a hunch, does Paint.NET work if you switch to the Windows Classic theme?

Well I'll be damned!! Yes, it does work when using classic....As you can tell by my screenshot, I use different, non-default visual styles--I have hacked my uxtheme.dll. On the screenshot I provide, the visual style is actually being run via a 3rd party application called WindowBlinds (WB). When I use WB, I turn of the MS Theme Service as well..... I hope some of this helps. Guess now I can play around w/ Paint.net a little; I do hope you can figure out the compatibility issue that seems apparent (it'd be nice to not have to switch to Classic everytime to use it)....Let me know if you'd like me to try something that could help..

Link to comment
Share on other sites

What happens if you have WB enabled, but also leave the Themes service turned on? And what's the name of the theme you're using, and is there a place I can download it?

I'm trying to figure out the exact scenario that causes this so I can file a bug on the .NET guys. This is not a bug in Paint.NET, but will affect any .NET app that uses the same stuff in the framework that we do.

The Paint.NET Blog: https://blog.getpaint.net/

Donations are always appreciated! https://www.getpaint.net/donate.html

forumSig_bmwE60.jpg

Link to comment
Share on other sites

Running the native windows Themes service & WB at the same time still results in the "unhandled" error when opening paint.net....It's hard for me to believe that there's an issue w/ running this on machines using anything other than Classic...I am a member on a couple different forums where members are running all sorts of visual styles--either w/ the theme service turned on (w/ a hacked uxtheme.dll) or w/ it off (via WB), and most seem to be able to run Paint.net just fine.

The visual style is called Luna Element 5, and you can get it here--- http://www.deviantart.com/deviation/29511577/

Link to comment
Share on other sites

IIRC, Luna Element 5 isnt a WB theme. it's just a regular Visual Style. right now im using it and it doesn't cause me problems. i don't know why but it doesn't.

Yep, LE5 is a VS, not WB....I used Skin Studio to convert it for WB use. I've found that WB is more "efficient" than the native Windows theme service, so I turn of theme service & run most everyhting through WB now...

Link to comment
Share on other sites

Hmm. Sounds like it might just be a WindowBlinds bug then. You might try pinging the author about that.

Just tried a quick test--I unloaded WB, turned on the Windows theme service and used visual styles (i.e., non-classic, Windows XP style). Paint.net opens just fine. So, unfortunately, there does appear to be an incompatibility between paint & WB. Too bad, paint.net looks to be a nice app; I like running themes through WB, so giving that up is a deal-breaker for me. I'll post about it on a couple forums that cater to WB & visual styles users to confirm other WB users are having the same issues...Thanks for your responses.

Link to comment
Share on other sites

Now that the reason for the error has been found i have a solution too.

Open Winblinds go under Per Application ( Settings)

and add a setting for Paint.NET and try other setting there if you want

I have a Total exlusion so that it doesn't skin it and now it works fine.

Link to comment
Share on other sites

Now that the reason for the error has been found i have a solution too.

Open Winblinds go under Per Application ( Settings)

and add a setting for Paint.NET and try other setting there if you want

I have a Total exlusion so that it doesn't skin it and now it works fine.

Huh, can't believe that work-around never occurred to me!! I've done that w/ several apps in the past...Thanks for the heads-up, it seems to have worked...Now to figure out how to use this!!

Link to comment
Share on other sites

  • 1 month later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...