[219] Complete VS Hangs Getting Worse - During Keyboard Options

Hello,

Well, now I just did the textual search in the keyboard options (to find
a RS item which lost its shortcut binding), which resulted in a
completely frozen VS as described in the Screensaver thread.

I'm afraid I can't use 219 any more with these characteristics.

Stack traces follow.

Cheers,

Christian


> mscorlib.dll!System.Threading.Monitor.Wait(object obj, int
millisecondsTimeout, bool exitContext) + 0x14 bytes
JetBrains.ReSharper.Psi.dll!
JetBrains.ReSharper.Psi.Impl.Caches2.CacheUpdateThread.Run() Line 71 +
0x10 bytes C#
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart_Context
(object state) + 0x3b bytes
mscorlib.dll!System.Threading.ExecutionContext.Run
(System.Threading.ExecutionContext executionContext,
System.Threading.ContextCallback callback, object state) + 0x81 bytes

mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x40
bytes


Thread 3840 JetBrains.ReSharper.AnimatedBitmapPainter
> JetBrains.ReSharper.UnitTestSupport.dll!
JetBrains.ReSharper.UnitTestSupport.UI.AnimatedBitmapPainter.AnimatorThr
eadProc() Line 55 C#
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart_Context
(object state) + 0x3b bytes
mscorlib.dll!System.Threading.ExecutionContext.Run
(System.Threading.ExecutionContext executionContext,
System.Threading.ContextCallback callback, object state) + 0x81 bytes

mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x40
bytes



> mscorlib.dll!System.Threading.WaitHandle.WaitOne(long timeout,
bool exitContext) + 0x2e bytes
mscorlib.dll!System.Threading.WaitHandle.WaitOne(int
millisecondsTimeout, bool exitContext) + 0x23 bytes
System.Windows.Forms.dll!
System.Windows.Forms.Control.WaitForWaitHandle
(System.Threading.WaitHandle waitHandle =
{System.Threading.ManualResetEvent}) + 0xa1 bytes
System.Windows.Forms.dll!
System.Windows.Forms.Control.MarshaledInvoke
(System.Windows.Forms.Control caller, System.Delegate method, object[]
args, bool synchronous) + 0x36d bytes
System.Windows.Forms.dll!System.Windows.Forms.Control.Invoke
(System.Delegate method, object[] args) + 0x48 bytes
System.Windows.Forms.dll!
System.Windows.Forms.WindowsFormsSynchronizationContext.Send
(System.Threading.SendOrPostCallback d, object state) + 0x61 bytes
System.dll!
Microsoft.Win32.SystemEvents.SystemEventInvokeInfo.Invoke(bool
checkFinalization = true, object[] args = ) + 0x68 bytes

System.dll!Microsoft.Win32.SystemEvents.RaiseEvent(bool
checkFinalization = true, object key = , object[] args =
) + 0x106 bytes
System.dll!Microsoft.Win32.SystemEvents.OnUserPreferenceChanged
(int msg, System.IntPtr wParam, System.IntPtr lParam) + 0x6f bytes
System.dll!Microsoft.Win32.SystemEvents.WindowProc(System.IntPtr
hWnd = 656626, int msg = 8218, System.IntPtr wParam = 1, System.IntPtr
lParam = 286464632) + 0x29d bytes


> System.Runtime.Remoting.dll!
System.Runtime.Remoting.Channels.Ipc.IpcServerChannel.Listen() + 0x244
bytes
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart_Context
(object state) + 0x3b bytes
mscorlib.dll!System.Threading.ExecutionContext.Run
(System.Threading.ExecutionContext executionContext,
System.Threading.ContextCallback callback, object state) + 0x81 bytes

mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x40
bytes

1 comment
Comment actions Permalink

JetBrains.ReSharper.UnitTestSupport.UI.AnimatedBitmapPainter.AnimatorThr
eadProc() Line 55 C#


Just because I noticed the UnitTestSupport in one of the stack traces: I
had an open UnitTestRunner in an auto-hidden window.

Cheers,

Christian


0

Please sign in to leave a comment.