Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / CLR / November 2006

Tip: Looking for answers? Try searching our database.

Exception on Application.Exit()

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Armin Prosch - 29 Oct 2006 22:54 GMT
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
Scott M. - 29 Oct 2006 23:29 GMT
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/]

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.