Geek Answers Handbook

Need help decrypting C # stack trace

I have an application that blocks the GUI thread, and I used WinDbg with the "! Clrstack" command to get this stack trace, but I cannot figure out where the problem is. All of these methods look like framework methods, and none of them are mine. Any help is appreciated. I apologize for the long lines

OS Thread Id: 0x724 (0) ESP EIP 0012ec88 7c90e4f4 [HelperMethodFrame_1OBJ: 0012ec88] System.Threading.WaitHandle.WaitOneNative(Microsoft.Win32.SafeHandles.SafeWaitHandle, UInt32, Boolean, Boolean) 0012ed34 792b687f System.Threading.WaitHandle.WaitOne(Int64, Boolean) 0012ed50 792b6835 System.Threading.WaitHandle.WaitOne(Int32, Boolean) 0012ed64 7b6f192f System.Windows.Forms.Control.WaitForWaitHandle(System.Threading.WaitHandle) 0012ed78 7ba2d0bb System.Windows.Forms.Control.MarshaledInvoke(System.Windows.Forms.Control, System.Delegate, System.Object[], Boolean) 0012ee18 7b6f328c System.Windows.Forms.Control.Invoke(System.Delegate, System.Object[]) 0012ee4c 7b920717 System.Windows.Forms.WindowsFormsSynchronizationContext.Send(System.Threading.SendOrPostCallback, System.Object) 0012ee64 7a924102 Microsoft.Win32.SystemEvents+SystemEventInvokeInfo.Invoke(Boolean, System.Object[]) 0012ee98 7a922833 Microsoft.Win32.SystemEvents.RaiseEvent(Boolean, System.Object, System.Object[]) 0012eee4 7a923d2f Microsoft.Win32.SystemEvents.OnUserPreferenceChanged(Int32, IntPtr, IntPtr) 0012ef04 7aa8f184 Microsoft.Win32.SystemEvents.WindowProc(IntPtr, Int32, IntPtr, IntPtr) 0012ef08 003620a4 [InlinedCallFrame: 0012ef08] 0012f0cc 7b1d8cce System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32, Int32, Int32) 0012f168 7b1d8937 System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext) 0012f1bc 7b1d8781 System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext) 0012f1ec 7b195911 System.Windows.Forms.Application.Run(System.Windows.Forms.Form) 0012f200 00eb0ebb WinForms1.Program.Main() 0012f69c 79e71b4c [GCFrame: 0012f69c]
+6
stack-trace c #
source share
3 answers

This code does not seem to be the true cause of the problem. See if one of these pages helps:

Update: Fixed URL of the first page.

+8
source share

Another answer comes from this Aaron Lerch. I really like the "filtered breakpoint for someone else code" part. I think that would save me a couple of days.

http://www.aaronlerch.com/blog/2008/12/15/debugging-ui/

+3
source share

I had a similar problem and found the culprit in our code.

Technique used: 0. Verify that in Spy ++ there are only two unmanaged threads with controls (WinForms and GDI +):

 public static class ThreadingHelper_NativeMethods { [DllImport("user32.dll")] public static extern bool IsGUIThread(bool bConvert); }

call this from the user interface thread after init:

 // This code forces initialization of .NET BroadcastEventWindow to the UI thread. // http://social.msdn.microsoft.com/Forums/en-US/netfxbcl/thread/fb267827-1765-4bd9-ae2f-0abbd5a2ae22 if (ThreadingHelper_NativeMethods.IsGUIThread(false)) { Microsoft.Win32.SystemEvents.InvokeOnEventsThread(new MethodInvoker(delegate() { int x = 0; })); }

  • Remember the managed id from the Ui stream in a singleton class.

  • Find all UserControls defined in our code. In each control constructor, before calling InitializeComponent (), I placed a code that checks the current thread identifier for the main thread identifier. If they are not equal, Assert (false).

  • Subscribe to SystemEvents.UserPreferencesChanging. Debug.Assert (false) in the handler: this happens before SystemEvents.UserPreferencesChanged, so the debugger will hopefully pause here.

  • Check the list of subscribers to SystemEvents in the debugger. Find the subscriber in the _handles dictionary of listings. Opening the SynchronizationContext of each callback should reveal the problem: the same thread identifier as for the control created in the thread other than the UI. SystemEvents will execute an event handler in this thread, blocking the UI thread.

+1
source share

More articles:


All Articles