Home Dashboard Directory Help
Search

Crash when using Find in Files in a large project by Jason Coyne


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


4
0
Sign in
to vote
Type: Bug
ID: 586669
Opened: 8/16/2010 11:03:49 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

Visual Studio 2010 crashes when running Find in Files on a very large solution (100+Projects)

---------------------------
Microsoft Visual Studio
---------------------------
Visual Studio has encountered an exception. This may be caused by an extension.


You can get more information by running the application together with the /log parameter on the command line, and then examining the file 'C:\Documents and Settings\User\Application Data\Microsoft\VisualStudio\10.0\ActivityLog.xml'.

Details
Sign in to post a comment.
Posted by Microsoft on 8/23/2010 at 1:32 AM
Hi, given that we have not heard back from you in 7 days. We will go ahead and close this Connect Issue. If you get a chance to review and provide the information requested earlier, you can go ahead and reactivate this issue.
Posted by Microsoft on 8/19/2010 at 8:48 PM
Please upload file to
https://sftus.one.microsoft.com/choosetransfer.aspx?key=1d9ea00a-8c28-4453-819d-30256b0b9625
Password is 9f]XUpR2Vq
Posted by Microsoft on 8/16/2010 at 7:00 PM
Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

It may help if you provide us with a mini dump file and call stack. You can use the following steps to get a dump file:

************************************************************
Note: Please zip the file and use "FeedbackID-586669" as prefix of the file name.

************************************************************

1. Start Visual Studio.
2. Start another instance of VS.
3. In the second instance click Tools | Attach to Process...
4. In the list of processes locate devenv.exe.
5. Click Select... and explicitly choose 'Native' and 'Managed' code.
6. Click OK and OK to close Select dialog and Attach to Process dialog.
7. Go back to the first instance of VS and repro the crash\hang.
8. Upon the crash\hang, control should go to the second instance of VS.
9. In the second instance click Debug | Save Mini Dump (without heap).

If you are running the VB profile you will not see the Save Dump As menu item. To add this menu item:
a. Select Tools -> Customize
b. Select the Commands tab
c. Select Debug from the “Menu bar” dropdown
d. Click “Add Command…”
e. Select Debug from the Categories list.
f. Find the “Save Dump As” entry in the Commands window.
g. Click OK (the “Save Dump As…” command is added to the top of the Debug menu).
h. Click “Close”

You can get detailed steps about how to get the dump file and call stack at http://blogs.msdn.com/debugger/archive/2009/12/30/what-is-a-dump-and-how-do-i-create-one.aspx

After that, please upload file to workspace:

https://sftus.one.microsoft.com/choosetransfer.aspx?key=3742328a-8d23-46e0-921d-c0c454a3f6a8
Password is X5eRup%anJ

It would be greatly appreciated if you could provide us with that information as quickly as possible. If we do not hear back from you within 7 days, we will close this issue.

Thanks again for your efforts and we look forward to hearing from you.
Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 8/16/2010 at 5:03 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.
File Name Submitted By Submitted On File Size  
ActivityLog.xml (restricted) 8/16/2010 -