Not enough storage is available to process this command

[Guest]

at System.Windows.Forms.Form.UpdateLayered()
at System.Windows.Forms.Form.OnHandleCreated(EventArgs e)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmCreate(Message& m)
at System.Windows.Forms.Form.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)

thats all I get. No line number. Nothing.

Where in the hell do I start?

I have a feeling from what i've read that it could be a memory /resource
leak on the gui coding that manifests after a while, but we have the same
code running in .net 1.1 and we do not get ANY leaks or messages as this. We
converted this code to .net 2.0 and the error has started to appear.

I'd love any help at all that we can get.

 

[Guest]

What's your code doing when this error happens?

 

[Guest]

f**in nothing.

It is displaying a form for the users. (its a greeting program, it takes a
biometric identifier, and then puts a record in the DB to denote to the
solution that the client has checked in.

I would love to tell you exactly what provokes it, but as you'll notice the
bug is occuring in the message loop from winforms, not from direct call from
my code. Hence my, wtf do I start? comment.

We would love to use VS2005 but right now we are looking at rolling back.

I am a registered MSDN subscriber, and I would REALLY appreciate some MS
input on this. Our code runs fine in .net 1.1, but not 2.0. Help me start
debugging please, before I have to start at line 1, and find leaks and
isolate issues (the error takes around 25/30 mins to manifest under normal
conditions, and results in a loop of error messages, with most clients
forcibly rebooting the machine to resolve it.

 

[Kevin Spencer]

Have you tried stepping through your app code, using F10?

--
HTH,

Kevin Spencer
Microsoft MVP

Printing Components, Email Components,
FTP Client Classes, Enhanced Data Controls, much more.
DSI PrintManager, Miradyne Component Libraries:
http://www.miradyne.net

 

[Guest]

the bug doesn't occur on our testing rig.

Nor does it manfiest immediately. the system is used for around an hour,
and then it goes into a loop of these messages.

The error as you can see is OCCURING in winforms callbacks. I realise that
there is obviously something wrong in our app as everyone would be
complaining if the every winforms app did this.

Would I be correct in saying this is a memory/resource leak of windows API
handles. I've read somewhere that the desktop UI derives its memory from a
special pool or something, and that this could become full due to a
leak/recreate resource style bug. I just need some affirmation before I
spend a day looking through the code for leaks. And the type of leak I'm
looking for, if this is the problem at all.

 

[Kevin Spencer]

It's entirely possible that you're experiencing a memory leak, as the
System.Windows.Forms.Control class (from which all Controls, including Form
are derived) exposes unmanaged underlying Windows Controls. This is why all
Controls implement IDisposable. You could start by checking to ensure that
all of your Controls are being Disposed properly.

--
HTH,

Kevin Spencer
Microsoft MVP

Printing Components, Email Components,
FTP Client Classes, Enhanced Data Controls, much more.
DSI PrintManager, Miradyne Component Libraries:
http://www.miradyne.net

 

[Guest]

I didn't write this code, I merely migrated the codebase.

Doesn't it seem strange though that this bug hasn't manifested itself until
we went to .net 2.0?

Either way you believe the same as me, that a resource leak is the most
likely culprit?