Geek Answers Handbook

Application crash without any exception

I have a multithreaded .NET C # application, it uses Direct3D 9/10 and XAudio2. (Direct3D has access to only one stream, the same for XAudio2. Direct3D is not a problem, because the error appears in either DX9 mode or DX10 mode without any changes in its behavior.)

Sometimes (there are some areas that give this problem randomly), this application crashes quite imperceptibly. Even if the application is launched through the visual studio using the debugger, it crashes without giving any exception. (Start by saying that “applicationname.svchost.exe crashed, etc .... do you want to debug?” If I click “yes”, it tells me: “you cannot debug an application that is already closed. )

Unable to find out the cause of the accident? Because I have run out of ideas, the debugger does not give me any information at all. Without an exception, I can’t even make a stacktrace or a dump .: P (I assume that this is a synchronization problem (even the thought in this area I do only sequential work ...), but hey why doesn't it throw an exception ?: |)

In areas where the problem arises, I upload a reload of a series of classes related to the novel (in a sequential kernel, so I doubt it could be a problem) and start new music through XAudio2. (By the way, what is the multi-threaded view of XAudio2? Is it safe to call from multiple threads?)

Thanks for the help.

PS Is there software to connect to my monitor for all calls and tells me that the last call before the failure?

+7
multithreading c # directx
source share
2 answers

You should try using Windbg , a crash dump analysis should indicate a problem, if your suspicion is correct and this is the synchronization of the problem, the cause of the problem can be difficult to determine.

+4
source share

Have you checked the event logs in the Windows Control Panel? Any error of any type is always recorded in this section with minimal details.

I once had an application that crashed without exception, and the only help I found was the event log viewer, in which I found that the source of the crash was a StackOverflowException.

+2
source share

More articles:


All Articles