Be prepared, this is a tricky one. One of my customers he is building a proof of concept using my software components. When running outside the debugger, the application will hang, using 100% CPU in the main thread. At this point attaching the debugger is
unsuccessful. When running inside the debugger, the application runs fine. (.NET framework 3.5, Windows 7 Ultimate x86, running in VirtualBox (virtual environment)).
Using Process Explorer I've tried to find some hints as to what's going on. Showing a callstack in PE at some arbitrary point when the app hangs is shown at the bottom of this post. The one line that caught my eye was this:
I googled around a bit, looks like a number of people ran into this, but nobody had found the true cause of/solution to this problem. One that came close was mentioning a patch for .NET framework 1.1, but there seems no information on later framework versions:
Some more details from my customer seem to point in the direction of GraphicsPath, which is used quite intensively and I know this class does a fair bit of switching to native land and back (PInvoke, also mentioned in the patch above).
We really need to get this one solved, so let me know what to do to get some developer support on this one.
View Complete Post