NullReferenceException in Windows.Forms.Label?

  • Thread starter Thread starter Chris Jones
  • Start date Start date
C

Chris Jones

One of the users of my application is reporting the following crash. The
stack trace looks like it's all internal to the Framework, so any ideas on
what this might be? I've never had the error myself and am not really sure
what to suggest...

System.NullReferenceException: Object reference not set to an instance of an
object.
at System.Windows.Forms.Label.CreateTextFormatFlags()
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.Label.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)
 
One of the users of my application is reporting the following crash. The
stack trace looks like it's all internal to the Framework, so any ideas
on what this might be? I've never had the error myself and am not really
sure what to suggest...
Click to expand...

Try and figure out what they were doing at the time.
Was it at startup?
Was it running a while?
Were they touch menus?
What sub screen were they on?
How is their harddisk space?
How much memory do they have?
Have they updated their windows to the latest release of .net?

If nothing else counts then try putting is some try catch blocks into
your code and write out to a flat file log. At least you can then narrow
down the problem.

Ta
Ken
 
Try and figure out what they were doing at the time.
Was it at startup?
Was it running a while?
Were they touch menus?
What sub screen were they on?
How is their harddisk space?
How much memory do they have?
Have they updated their windows to the latest release of .net?

If nothing else counts then try putting is some try catch blocks into
your code and write out to a flat file log. At least you can then narrow
down the problem.
Click to expand...

I've already got unhandled exception logging, that's how this error was
reported to me. As the stack trace is entirely within .NET Framework code I
don't see how I can narrow down the problem, since I have no way to debug
the code that is causing the error. Are there any known issues with this
part of the Framework?
 
Back
Top