Search

Visual Studio 2010 Crashes when "Find all Reference" is ran by MarcD

Closed
as Won't Fix Help for as Won't Fix

12
0
Sign in
to vote
Type: Bug
ID: 630657
Opened: 12/11/2010 8:57:11 PM
Access Restriction: Public
0
Workaround(s)
7
User(s) can reproduce this bug
Randomly but when it happens it happens every single time vs.net 2010 will crash when you do a "Find all References". If this happens it will always happen and there is no way around it. It just crashes repeatedly.

This has happened in the non-Beta version and it also happens in the beta version.

When I attach vs.net to the to VS.NET the exception that is thrown is as such:
AccessViolationException -> {"Attempted to read or write protected memory. This is often an indication that other memory is corrupt."}

at Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
at Microsoft.VisualStudio.Editor.Implementation.CommandChainNode.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
at Microsoft.VisualStudio.Editor.Implementation.CommandFilterWrapper.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
at Microsoft.VisualStudio.Editor.Implementation.VsTextViewAdapter.Exec(Guid& pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, IntPtr pvaIn, IntPtr pvaOut)
at Microsoft.VisualStudio.Editor.Implementation.VsMouseProcessor.DisplayContextMenu(Point mousePosition)
at Microsoft.VisualStudio.Editor.Implementation.VsMouseProcessor.PreprocessMouseRightButtonUp(MouseButtonEventArgs e)
at Microsoft.VisualStudio.Text.Utilities.WpfMouseProcessor.<>c__DisplayClass4b.<UIElement_MouseRightButtonUp>b__46()
at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.CallExtensionPoint(Object errorSource, Action call)
at Microsoft.VisualStudio.Text.Utilities.WpfMouseProcessor.UIElement_MouseRightButtonUp(Object sender, MouseButtonEventArgs e)
at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.InputFilterMessage(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)

I will also attach a memory dump taken with procmon of when this occurrs.
Details (expand)

Visual Studio/Silverlight/Tooling version

Visual Studio 2010 SP1 Beta

What category (if any) best represents this feedback?

Reliability

Steps to reproduce

Right now I have this large 4-5 project solution that the minute I open and go to the class and choose "Find All References" it crashes.

Product Language

English

Operating System

Windows 7

Operating System Language

English

Actual results

It crashes. When it crashes it will always crash at that point.

Expected results

I expect it to show me all of the references for the class. I am tired of this happening several times a day several times a week several times a month.
File Attachments
File Name Submitted By Submitted On File Size  
devenv_101211_224922.zip (restricted) 12/11/2010 -
Sign in to post a comment.
Posted by Microsoft on 7/3/2012 at 2:09 PM
Thank you for reporting this issue with Find All References and using Visual Studio. Unfortunately, we prioritized fixing other issues with more customer feedback for Visual Studio 2012 and did not plan to address this issue in Visual Studio 2010. If anyone finds this still occurring in Visual Studio 2012, please reactivate the bug with specific/detailed repro steps and we'll take a look.

Thanks,
Cathy Sullivan
Program Manager, Visual Studio Pro Experience Team
http://blogs.msdn.com/b/visualstudio
Posted by akjoshi on 4/16/2012 at 5:20 AM
I also face this problem very frequently, atleast 3-4 times a day.
Posted by MarcD on 5/22/2011 at 1:40 PM
It is 1/2 a year later and this problem still keeps happening. Like clockwork - literally ever freaking day.
Posted by Microsoft on 12/11/2010 at 10:39 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.