Not sure about your exception, but why are you not closing the form(s),
rather than calling Application.Exit(), which is a much more abrupt way of
terminating your application?
> Hello,
>
[quoted text clipped - 11 lines]
>
> Thanks in advance, Armin
Armin Prosch - 01 Nov 2006 20:52 GMT
That also doesn't help...
> Not sure about your exception, but why are you not closing the form(s),
> rather than calling Application.Exit(), which is a much more abrupt way of
[quoted text clipped - 15 lines]
> >
> > Thanks in advance, Armin
Oleg Starodumov - 02 Nov 2006 16:15 GMT
Can this problem be reproduced under native or mixed mode debugger?
If it can, what are the symptoms (when running under debugger), and what
is on the call stack?
If it cannot be reproduced in that way, try to attach debugger to the application
while it is showing the message, and obtain the call stack.
I would recommend to start with WinDbg or CDB in this case, as shown here:
http://www.debuginfo.com/articles/easywindbg.html#debugdeadlocks
What will be on the call stack of the thread that is showing the message?
--
Oleg
[VC++ MVP http://www.debuginfo.com/]