Exception on Application.Exit()

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

when my application shuts down via Application.Exit() I get a message box
with the text ["unknown software exception" 0x80000003 on .....]. In the
application I use DirectShow (via directshow.net) and managed DirectX.
Besides that I start a tcp listener in a seperate thread but gracefully close
it via thread.join(number of milliseconds).

This exception did not pop up 5 days ago. Does somebody know where I can
look at when debugging or just a few hints where to look at in the internet
or sdk?

Thanks in advance, Armin
 
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?
 
That also doesn't help...

Scott M. said:
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?

Armin Prosch said:
Hello,

when my application shuts down via Application.Exit() I get a message box
with the text ["unknown software exception" 0x80000003 on .....]. In the
application I use DirectShow (via directshow.net) and managed DirectX.
Besides that I start a tcp listener in a seperate thread but gracefully
close
it via thread.join(number of milliseconds).

This exception did not pop up 5 days ago. Does somebody know where I can
look at when debugging or just a few hints where to look at in the
internet
or sdk?

Thanks in advance, Armin
Click to expand...
Click to expand...
 
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?
 
Back
Top