Problems in VS2010RC

So I've downloaded and installed the RC of VS2010 Ultimate edition.  I've been running Beta2 previously, and mostly everything has been  working just fine. There was an occasional problem with resharper and  VS's stability, but that was fine; besides, it was much better that  VS2008 anyway, so..
But now I got build1612 of Resharper, and  things went downhill - badly. And build 1613 only made it worse!
I open Resharper->Options, then close them - VS crashes. Or, if it  doesnt crash, then the next click inside the code (anywhere) crashes  it. Code hilighting still does not work - it semi-worked (some were  hilighted, such as strings, others werent, such as namespaces). For some  reason, some of the icons in 1613 are missing in the Options dialog -  but I assume that is a temporary problem that will be solved quickly. I  wouldn't even mention it VS wouldn't crash after closing Resharper  Options. Hmm, what else....Ah! It crashes somewhat randomly - VS, that  is, not resharper. I would assume it is due to a resharper bug (though I  still have to check that).

I think that's about it for now. If any details are needed, I'll be  glad to contribute, since having Resharper by my side when developing is  a real god-send, so if I can help improve it, I will.

21 comments
Comment actions Permalink

Hello,

I open Resharper->Options, then close them - VS crashes. Or, if it
doesnt crash, then the next click inside the code (anywhere) crashes
it.


I cannot repro this behavior on fresh builds here. It would be very helpful
if you could capture a stack trace of the crash.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0
Comment actions Permalink

Hello Serge,

>> I open Resharper->Options, then close them - VS crashes. Or, if it
>>

I cannot repro this behavior on fresh builds here. It would be very
helpful if you could capture a stack trace of the crash.


You will find some entries in YouTrack with many Exceptions in the Options
Dialog
also for 1615. But it doesn't crash here.

Regards

Albert


0
Comment actions Permalink

OK, so the color hiliting is working perfectly in 1615. Thats great! As for crashes - it just crashed on me, seemingly randomly. All I did was look in the VS Options dialog, changed a few things (common text formatting options: always show line numbers), and pressed OK. And the Options dialog closed, a second went by, and VS crashed. As to capturing a stack trace: not very familiar with how to do that. A lilttle help? Thanks!

0
Comment actions Permalink

I also encounter VS2010RC crashes with Resharper 5.0 latest nightly build (currently 1616).

Particularly, when pressing right mouse button on identifier.

It could also be some incompatibility with Reflector plugin, because it always crashed with R# on right mouse button until I disabled "Hide overriden VS menu items".

I tried disabling VS integration in Reflector, but it also crashes with only Resharper installed, although probability is less than 100%.

Here is an example of stack trace of such crash (when I pressed right button hovering over function call):

> KernelBase.dll!_RaiseException@16()  + 0x58 bytes
  clr.dll!6a870050()  
  [Frames below may be incorrect and/or missing, no symbols loaded for clr.dll]
  clr.dll!6a870289()  
  Microsoft.VisualStudio.Platform.VSEditor.ni.dll!5d01cf00()  
  clr.dll!6a6e20de()  
  3185ada4()
  PresentationCore.ni.dll!674b0286()  
  PresentationCore.ni.dll!674af77e()  
  mscorlib.ni.dll!69b50e93()  
  mscorlib.ni.dll!69b24fb6()  
  mscorlib.ni.dll!69b250f0()  
  WindowsBase.ni.dll!67a2a1fc()  
  WindowsBase.ni.dll!67a25fbe()  
  WindowsBase.ni.dll!67a2614f()  
  WindowsBase.ni.dll!67a27782()  
  WindowsBase.ni.dll!67a276b1()  
  WindowsBase.ni.dll!67a2755f()  
  WindowsBase.ni.dll!67a27496()  
  WindowsBase.ni.dll!67a25a40()  
  WindowsBase.ni.dll!67a26fc0()  
  user32.dll!_InternalCallWinProc@20()  + 0x23 bytes
  user32.dll!_UserCallWinProcCheckWow@32()  + 0xb7 bytes
  user32.dll!_DispatchMessageWorker@8()  + 0xed bytes
  user32.dll!_DispatchMessageW@4()  + 0xf bytes
  msenv.dll!6aebd865()  
  msenv.dll!6aebd7e1()  
  msenv.dll!6aec1eb7()  
  msenv.dll!6aec1d49()  
  msenv.dll!6aec1d16()  
  msenv.dll!6aec1c58()  
  msenv.dll!6ae73a55()  
  devenv.exe!2f317c6d()  
  devenv.exe!2f3184a4()  
  devenv.exe!2f31959c()  
  devenv.exe!2f31960c()  
  kernel32.dll!@BaseThreadInitThunk@12()  + 0x12 bytes
  ntdll.dll!___RtlUserThreadStart@8()  + 0x27 bytes
  ntdll.dll!__RtlUserThreadStart@8()  + 0x1b bytes

0
Comment actions Permalink

Hello,

You will find some entries in YouTrack with many Exceptions in the
Options Dialog also for 1615. But it doesn't crash here.


If they're related to missing image resources, then they're most probably
unrelated (not being fatal in any sense).


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0
Comment actions Permalink

Hello,

It could also be some incompatibility with Reflector plugin,


Do you mean the Reflector Pro product that also has Visual Studio integration?
I'm afraid it's currently not included in our testing.

Here is en example of stack trace of such crash (when I pressed right
button hovering over function call):


Unfortunately, these are native-only stack traces, without .NET class/function
names resolved. To get the managed stack traces info, Visual Studio should
be instructed to debug with both Native (x86) and Managed (CLR4) engines
when attaching to the failing process. Or, since there're no symbols for
those native DLLs anyway, with only Managed (CLR4) engine.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0
Comment actions Permalink

Here is en example of stack trace of such crash (when I pressed right
button hovering over function call):


Unfortunately, these are native-only stack traces, without .NET class/function
names resolved. To get the managed stack traces info, Visual Studio should
be instructed to debug with both Native (x86) and Managed (CLR4) engines
when attaching to the failing process. Or, since there're no symbols for
those native DLLs anyway, with only Managed (CLR4) engine.


Oops! Sory for that.

Here is another stack trace of the crash:

> Microsoft.VisualStudio.Platform.VSEditor.dll!Microsoft.VisualStudio.Language.Intellisense.Implementation.QuickInfoPresenterControl.OnCreateAutomationPeer() + 0x168 bytes
  PresentationCore.dll!System.Windows.UIElement.CreateAutomationPeer() + 0x46 bytes
  PresentationCore.dll!System.Windows.Automation.Peers.UIElementAutomationPeer.CreatePeerForElement(System.Windows.UIElement element) + 0x11 bytes
  PresentationCore.dll!System.Windows.Automation.Peers.UIElementAutomationPeer.iterate(System.Windows.DependencyObject parent = {System.Windows.Documents.NonLogicalAdornerDecorator}, System.Windows.Automation.Peers.UIElementAutomationPeer.IteratorCallback callback = {Method = {System.Reflection.RuntimeMethodInfo}}) + 0x6b bytes
  PresentationCore.dll!System.Windows.Automation.Peers.UIElementAutomationPeer.iterate(System.Windows.DependencyObject parent = {System.Windows.Controls.Decorator}, System.Windows.Automation.Peers.UIElementAutomationPeer.IteratorCallback callback = {Method = {System.Reflection.RuntimeMethodInfo}}) + 0xcf bytes
  PresentationCore.dll!System.Windows.Automation.Peers.UIElementAutomationPeer.iterate(System.Windows.DependencyObject parent = {System.Windows.Controls.Primitives.PopupRoot}, System.Windows.Automation.Peers.UIElementAutomationPeer.IteratorCallback callback = {Method = {System.Reflection.RuntimeMethodInfo}}) + 0xcf bytes
  PresentationCore.dll!System.Windows.Automation.Peers.UIElementAutomationPeer.GetChildrenCore() + 0x40 bytes
  PresentationCore.dll!System.Windows.Automation.Peers.AutomationPeer.EnsureChildren() + 0x1e bytes
  PresentationCore.dll!System.Windows.Automation.Peers.AutomationPeer.UpdateChildrenInternal(int invalidateLimit = 20) + 0x3e bytes
  PresentationCore.dll!System.Windows.Automation.Peers.AutomationPeer.UpdateChildren() + 0xa bytes
  PresentationCore.dll!System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree() + 0x338 bytes
  PresentationCore.dll!System.Windows.ContextLayoutManager.fireAutomationEvents() + 0xd3 bytes
  PresentationCore.dll!System.Windows.ContextLayoutManager.UpdateLayout() + 0x7ce bytes
  PresentationCore.dll!System.Windows.ContextLayoutManager.UpdateLayoutCallback(object arg) + 0x19 bytes
  PresentationCore.dll!System.Windows.Media.MediaContext.InvokeOnRenderCallback.DoWork() + 0x10 bytes
  PresentationCore.dll!System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks() + 0x6f bytes
  PresentationCore.dll!System.Windows.Media.MediaContext.RenderMessageHandlerCore(object resizedCompositionTarget = null) + 0x8a bytes
  PresentationCore.dll!System.Windows.Media.MediaContext.RenderMessageHandler(object resizedCompositionTarget) + 0x2c bytes
  WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate callback, object args, int numArgs) + 0x53 bytes
  WindowsBase.dll!MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(object source = {System.Windows.Threading.Dispatcher}, System.Delegate method, object args, int numArgs, System.Delegate catchHandler = null) + 0x42 bytes
  WindowsBase.dll!System.Windows.Threading.DispatcherOperation.InvokeImpl() + 0x8d bytes
  WindowsBase.dll!System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(object state) + 0x38 bytes
  mscorlib.dll!System.Threading.ExecutionContext.runTryCode(object userData) + 0x51 bytes
  mscorlib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x6a bytes
  mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool ignoreSyncCtx) + 0x7e bytes
  mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x2c bytes
  WindowsBase.dll!System.Windows.Threading.DispatcherOperation.Invoke() + 0x68 bytes
  WindowsBase.dll!System.Windows.Threading.Dispatcher.ProcessQueue() + 0x15e bytes
  WindowsBase.dll!System.Windows.Threading.Dispatcher.WndProcHook(System.IntPtr hwnd, int msg, System.IntPtr wParam, System.IntPtr lParam, ref bool handled) + 0x63 bytes
  WindowsBase.dll!MS.Win32.HwndWrapper.WndProc(System.IntPtr hwnd = 5575818, int msg = 49912, System.IntPtr wParam = 0, System.IntPtr lParam = 0, ref bool handled = false) + 0xbe bytes
  WindowsBase.dll!MS.Win32.HwndSubclass.DispatcherCallbackOperation(object o) + 0x7d bytes
  WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate callback, object args, int numArgs) + 0x53 bytes
  WindowsBase.dll!MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(object source = {System.Windows.Threading.Dispatcher}, System.Delegate method, object args, int numArgs, System.Delegate catchHandler = null) + 0x42 bytes
  WindowsBase.dll!System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Threading.DispatcherPriority priority, System.TimeSpan timeout, System.Delegate method, object args, int numArgs) + 0xb4 bytes
  WindowsBase.dll!MS.Win32.HwndSubclass.SubclassWndProc(System.IntPtr hwnd = 5575818, int msg = 49912, System.IntPtr wParam = 0, System.IntPtr lParam = 0) + 0x104 bytes
  user32.dll!_InternalCallWinProc@20()  + 0x23 bytes
  user32.dll!_UserCallWinProcCheckWow@32()  + 0xb7 bytes
  user32.dll!_DispatchMessageWorker@8()  + 0xed bytes
  user32.dll!_DispatchMessageW@4()  + 0xf bytes
  msenv.dll!69f5d865()  
  [Frames below may be incorrect and/or missing, no symbols loaded for msenv.dll]
  msenv.dll!69f5d7e1()  
  msenv.dll!69f61eb7()  
  msenv.dll!69f61d49()  
  msenv.dll!69f61d16()  
  msenv.dll!69f61c58()  
  msenv.dll!69f13a55()  
  devenv.exe!2f777c6d()  
  devenv.exe!2f7784a4()  
  devenv.exe!2f77959c()  
  devenv.exe!2f77960c()  
  kernel32.dll!@BaseThreadInitThunk@12()  + 0x12 bytes
  ntdll.dll!___RtlUserThreadStart@8()  + 0x27 bytes
  ntdll.dll!__RtlUserThreadStart@8()  + 0x1b bytes

0
Comment actions Permalink

Hello Serge,

>> You will find some entries in YouTrack with many Exceptions in the
>> Options Dialog also for 1615. But it doesn't crash here.
>>

If they're related to missing image resources, then they're most
probably unrelated (not being fatal in any sense).


Not Missing Images Resources ....

http://youtrack.jetbrains.net/issue/RSRP-157056 (and much more)

Fresh-Installation, zero PlugIns.

Regards

Albert


0
Comment actions Permalink

As for the Reflector - yes, I mean the plugin in the Relector Pro (now in beta version).

Although I think that the main problem is integration of "View in Reflector" menu item (this functionality is going tol be in the free version).

0
Comment actions Permalink

And here is the exception:

-  $exception {System.InvalidOperationException: Trying to get automation peer on an already dismissed QuickInfo presenter.
   at Microsoft.VisualStudio.Language.Intellisense.Implementation.QuickInfoPresenterControl.OnCreateAutomationPeer()
   at System.Windows.UIElement.CreateAutomationPeer()
   at System.Windows.Automation.Peers.UIElementAutomationPeer.CreatePeerForElement(UIElement element)
   at System.Windows.Automation.Peers.UIElementAutomationPeer.iterate(DependencyObject parent, IteratorCallback callback)
   at System.Windows.Automation.Peers.UIElementAutomationPeer.iterate(DependencyObject parent, IteratorCallback callback)
   at System.Windows.Automation.Peers.UIElementAutomationPeer.iterate(DependencyObject parent, IteratorCallback callback)
   at System.Windows.Automation.Peers.UIElementAutomationPeer.GetChildrenCore()
   at System.Windows.Automation.Peers.AutomationPeer.EnsureChildren()
   at System.Windows.Automation.Peers.AutomationPeer.UpdateChildrenInternal(Int32 invalidateLimit)
   at System.Windows.Automation.Peers.AutomationPeer.UpdateChildren()
   at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
   at System.Windows.ContextLayoutManager.fireAutomationEvents()
   at System.Windows.ContextLayoutManager.UpdateLayout()
   at System.Windows.ContextLayoutManager.UpdateLayoutCallback(Object arg)
   at System.Windows.Media.MediaContext.InvokeOnRenderCallback.DoWork()
   at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
   at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
   at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)} System.Exception {System.InvalidOperationException}

0
Comment actions Permalink

Hello,

Thanks, elevated.

Shouldn't be fatal either, though.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0
Comment actions Permalink

Hello,

Hmm, very strange. Looks like Avalon has deferred updating of automation
peers and lost the peer owner object while waiting on the async queue.

"QuickInfoPresenterControl", however, could mean that it's related to the
tooltips ReSharper is showing over the code file. That's the indirect effect
of ReSharper being present in VS.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0
Comment actions Permalink

I guess, this will be hard to fix.

So - the crash when displaying context menu (right mouse button) at identifier is not reproducible (on other systems), is it?

What could I do to troubleshoot this?

0
Comment actions Permalink

Does this help? http://blogs.msdn.com/jasonz/archive/2010/02/15/patch-for-touch-screen-intellisense-issue-for-vs2010-rc.aspx


Sincerely,
Ilya Ryzhenkov

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


IK> I guess, this will be hard to fix.
IK>
IK> So - the crash when displaying context menu (right mouse button) at
IK> identifier is not reproducible (on other systems), is it?
IK>
IK> What could I do to troubleshoot this?
IK>
IK> ---
IK> Original message URL:
IK> http://www.jetbrains.net/devnet/message/5256757#5256757


0
Comment actions Permalink

Another place to look at is here: http://blogs.msdn.com/visualstudio/archive/2010/02/09/intellisense-crash-in-ui-automation.aspx

Sincerely,
Ilya Ryzhenkov

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


IK> I guess, this will be hard to fix.
IK>
IK> So - the crash when displaying context menu (right mouse button) at
IK> identifier is not reproducible (on other systems), is it?
IK>
IK> What could I do to troubleshoot this?
IK>
IK> ---
IK> Original message URL:
IK> http://www.jetbrains.net/devnet/message/5256757#5256757


0
Comment actions Permalink

This patch cleared up similar problems for me on the (ironically) PDC laptop with its multi-touch screen.

0
Comment actions Permalink

It didn't fully cease crashing, although it seemed to make the issue less likely at first.

It is probably VS issue, but it doesn't crash without Resharper installed.

Guess, I need to report the bug to Microsoft.

The stack trace is the same (displacement is a little different):

> Microsoft.VisualStudio.Platform.VSEditor.dll!Microsoft.VisualStudio.Language.Intellisense.Implementation.QuickInfoPresenterControl.OnCreateAutomationPeer() + 0x206 bytes

0
Comment actions Permalink

Yes, it is VS issue and it is already fixed for RTM, as I have been told.
Thanks for heads up!

Sincerely,
Ilya Ryzhenkov

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


IR> It didn't fully cease crashing, although it seemed to make the issue
IR> less likely at first.
IR>
IR> It is probably VS issue, but it doesn't crash without Resharper
IR> installed. Guess, I need to report the bug to Microsoft.
IR>
IR> The stack trace is the same (displacement is a little different):
IR>
>> Microsoft.VisualStudio.Platform.VSEditor.dll!Microsoft.VisualStudio.L
>> anguage.Intellisense.Implementation.QuickInfoPresenterControl.OnCreat
>> eAutomationPeer() + 0x206 bytes
>>
IR> ---
IR> Original message URL:
IR> http://www.jetbrains.net/devnet/message/5256768#5256768


0
Comment actions Permalink

fwiw, I'm still having this problem with ReSharper Build 5.0.1648.10, even after running the patch.  Usually, what happens is that Visual Studio 2010 RC will just crash, without my having done anything.

If v5/VS2010 is not more stable, I'm going to have to unload ReSharper for now, just to keep working.

From the event logs:

Application: devenv.exe

Framework Version: v4.0.30128

Description: The process was terminated due to an unhandled exception.

Exception Info: System.InvalidOperationException

Stack:

at Microsoft.VisualStudio.Language.Intellisense.Implementation.QuickInfoPresenterControl.OnCreateAutomationPeer()

at System.Windows.UIElement.CreateAutomationPeer()

at System.Windows.Automation.Peers.UIElementAutomationPeer.CreatePeerForElement(System.Windows.UIElement)

at System.Windows.Automation.Peers.UIElementAutomationPeer.iterate(System.Windows.DependencyObject, IteratorCallback)

at System.Windows.Automation.Peers.UIElementAutomationPeer.iterate(System.Windows.DependencyObject, IteratorCallback)

at System.Windows.Automation.Peers.UIElementAutomationPeer.iterate(System.Windows.DependencyObject, IteratorCallback)

at System.Windows.Automation.Peers.UIElementAutomationPeer.GetChildrenCore()

at System.Windows.Automation.Peers.AutomationPeer.EnsureChildren()

at System.Windows.Automation.Peers.AutomationPeer.UpdateChildrenInternal(Int32)

at System.Windows.Automation.Peers.AutomationPeer.UpdateChildren()

at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()

at System.Windows.ContextLayoutManager.fireAutomationEvents()

at System.Windows.ContextLayoutManager.UpdateLayout()

at System.Windows.ContextLayoutManager.UpdateLayoutCallback(System.Object)

at System.Windows.Media.MediaContext+InvokeOnRenderCallback.DoWork()

at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()

at System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object)

at System.Windows.Media.MediaContext.RenderMessageHandler(System.Object)

at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

at System.Windows.Threading.DispatcherOperation.InvokeImpl()

at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)

at System.Threading.ExecutionContext.runTryCode(System.Object)

at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)

at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

at System.Windows.Threading.DispatcherOperation.Invoke()

at System.Windows.Threading.Dispatcher.ProcessQueue()

at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)

at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

at System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)

at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

0
Comment actions Permalink

Hello Kevin,

They said they fixed this for RTM. I know, it won't help you, but it crashes
this way even without ReSharper...


Sincerely,
Ilya Ryzhenkov

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


KD> fwiw, I'm still having this problem with ReSharper Build
KD> 5.0.1648.10, even after running the patch.  Usually, what happens is
KD> that Visual Studio 2010 RC will just crash, without my having done
KD> anything.
KD>
KD> If v5/VS2010 is not more stable, I'm going to have to unload
KD> ReSharper for now, just to keep working.
KD>
KD> From the event logs:
KD>
KD> Application: devenv.exe
KD>
KD> Framework Version: v4.0.30128
KD>
KD> Description: The process was terminated due to an unhandled
KD> exception.
KD>
KD> Exception Info: System.InvalidOperationException
KD>
KD> Stack:
KD>
KD> at
KD> Microsoft.VisualStudio.Language.Intellisense.Implementation.QuickInf
KD> oPresenterControl.OnCreateAutomationPeer()
KD>
KD> at System.Windows.UIElement.CreateAutomationPeer()
KD>
KD> at
KD> System.Windows.Automation.Peers.UIElementAutomationPeer.CreatePeerFo
KD> rElement(System.Windows.UIElement)
KD>
KD> at
KD> System.Windows.Automation.Peers.UIElementAutomationPeer.iterate(Syst
KD> em.Windows.DependencyObject, IteratorCallback)
KD>
KD> at
KD> System.Windows.Automation.Peers.UIElementAutomationPeer.iterate(Syst
KD> em.Windows.DependencyObject, IteratorCallback)
KD>
KD> at
KD> System.Windows.Automation.Peers.UIElementAutomationPeer.iterate(Syst
KD> em.Windows.DependencyObject, IteratorCallback)
KD>
KD> at
KD> System.Windows.Automation.Peers.UIElementAutomationPeer.GetChildrenC
KD> ore()
KD>
KD> at System.Windows.Automation.Peers.AutomationPeer.EnsureChildren()
KD>
KD> at
KD> System.Windows.Automation.Peers.AutomationPeer.UpdateChildrenInterna
KD> l(Int32)
KD>
KD> at System.Windows.Automation.Peers.AutomationPeer.UpdateChildren()
KD>
KD> at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
KD>
KD> at System.Windows.ContextLayoutManager.fireAutomationEvents()
KD>
KD> at System.Windows.ContextLayoutManager.UpdateLayout()
KD>
KD> at
KD> System.Windows.ContextLayoutManager.UpdateLayoutCallback(System.Obje
KD> ct)
KD>
KD> at System.Windows.Media.MediaContext+InvokeOnRenderCallback.DoWork()
KD>
KD> at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
KD>
KD> at
KD> System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Ob
KD> ject)
KD>
KD> at
KD> System.Windows.Media.MediaContext.RenderMessageHandler(System.Object
KD> )
KD>
KD> at
KD> System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.De
KD> legate, System.Object, Int32)
KD>
KD> at
KD> MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Obje
KD> ct, System.Delegate, System.Object, Int32, System.Delegate)
KD>
KD> at System.Windows.Threading.DispatcherOperation.InvokeImpl()
KD>
KD> at
KD> System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext
KD> (System.Object)
KD>
KD> at System.Threading.ExecutionContext.runTryCode(System.Object)
KD>
KD> at
KD> System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaran
KD> teedCleanup(TryCode, CleanupCode, System.Object)
KD>
KD> at
KD> System.Threading.ExecutionContext.RunInternal(System.Threading.Execu
KD> tionContext, System.Threading.ContextCallback, System.Object)
KD>
KD> at
KD> System.Threading.ExecutionContext.Run(System.Threading.ExecutionCont
KD> ext, System.Threading.ContextCallback, System.Object, Boolean)
KD>
KD> at
KD> System.Threading.ExecutionContext.Run(System.Threading.ExecutionCont
KD> ext, System.Threading.ContextCallback, System.Object)
KD>
KD> at System.Windows.Threading.DispatcherOperation.Invoke()
KD>
KD> at System.Windows.Threading.Dispatcher.ProcessQueue()
KD>
KD> at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32,
KD> IntPtr, IntPtr, Boolean ByRef)
KD>
KD> at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr,
KD> Boolean ByRef)
KD>
KD> at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
KD>
KD> at
KD> System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.De
KD> legate, System.Object, Int32)
KD>
KD> at
KD> MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Obje
KD> ct, System.Delegate, System.Object, Int32, System.Delegate)
KD>
KD> at
KD> System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Thread
KD> ing.DispatcherPriority, System.TimeSpan, System.Delegate,
KD> System.Object, Int32)
KD>
KD> at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr,
KD> IntPtr)
KD>
KD> ---
KD> Original message URL:
KD> http://www.jetbrains.net/devnet/message/5260160#5260160


0

Please sign in to leave a comment.