Home Dashboard Directory Help
Search

Find Definition of Object (Shift+F12) more than two or three time hangs Visual Studio by Shafqat_ali


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


1
0
Sign in
to vote
Type: Bug
ID: 709821
Opened: 11/30/2011 4:10:07 AM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

I am using Visual Studio 2010 with ServicePack 1, on Windows Vista. I have a website which contains about 30 pages and Entity faramwork as Data Layer.

I have Search for references of one of my Custom Types i.e. Product by pressing (Shift+F12)
it worked fine but when i do it 2,3 time more then it Visual Studio will Slows down dramatically, while searching and after searching also. When i open TaskManager windows this shows me the amount of memory used by Visual Studio (Devenv.exe) is very high.

When i terminate the process and open the VS again i worked fine as my system do. When i repeat the about mentioned steps again it will do same and i have to terminate it again and again....
Details
Sign in to post a comment.
Posted by Shafqat_ali on 12/26/2011 at 1:30 AM
Hello,
Sorry for having too late to reply. There was problem with Vista i have installed some update and restart the system. And it is working fine now.
Posted by Microsoft on 12/25/2011 at 10:59 PM
Thank you for submitting feedback on Visual Studio 2010 and the .NET Framework. Since we have not heard back from you we will close the issue. If you need further assistance on this or any other pre-release product issues in the future, please feel free to contact us and we will be happy to help.
Posted by Microsoft on 12/16/2011 at 2:31 AM
Hello,

Sorry for bothering again. Is there any update?

It would be greatly appreciated if you could provide us with that information as quickly as possible.

Thanks you
Posted by Microsoft on 12/9/2011 at 1:47 AM
Hello,

Sorry for bothering. Is there any update? To investigate a performance issue, a trace file is needed.

It would be greatly appreciated if you could provide us with that information as quickly as possible.

Thanks you
Posted by Microsoft on 12/4/2011 at 10:54 PM
Hi Shafqat_ali,

Thanks for your quick response. But I cannot find the trace file in the zipped file you provided.

Could you please help to capture a trace file and send it to us?

Thanks again for your efforts and we look forward to hearing from you.
Posted by Shafqat_ali on 12/4/2011 at 10:34 PM
I have tried all the steps but problem still exists. So please send me update about that.

I have send all the inforamtion on following :
https://sftasia.one.microsoft.com/choosetransfer.aspx?key=5d606cdd-4289-47af-bd1d-6ab77876dfe7

Thanks Shafqat,
Software Engineer
Posted by Microsoft on 12/4/2011 at 7:31 PM
Hello,

Sorry for bothering. Is there any update?

It would be greatly appreciated if you could provide us with that information as quickly as possible.

Thanks you
Posted by MS-Moderator09 [Feedback Moderator] on 11/30/2011 at 6:34 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.

Could you please help to confirm is this issue still reproducible with Visual Studio in safe mode? To do this, you need launch Visual Studio by "devenv.exe /safemode".
If this issue goes away with Visual Studio in safe mode, please help to send us a copy of your plugin info. To get your plugin info, you can launch an instance of VS, select "Help"-->"About Microsoft Visual Studio", hit "Copy Info" and paste it into a text file, then send us the text file.

And it may help if you provide us with:

1. You can run a DXDIAG and send us the output? (Type DXDiag in Vista/Win Search Box, Click Save All Information, and then e-mail the resulting dxdiag.txt file: http://support.microsoft.com/kb/190900).

2. Gather some ETW traces around your scenario: In order to do this, please download the VS performance tool from: http://visualstudiogallery.msdn.microsoft.com/en-us/e8649e35-26b1-4e73-b427-c2886a0705f4 Please read the "Performance Diagnostics Tool User Guide" document (a shortcut to it should appear on your desktop after install) on steps to generate a trace. Please note that when you uninstall the tool, the settings.ini file will not be removed as it contains your user settings. Also, unfortunately this tool does not work on XP. Once you collected traces, we have a secure site where you can upload your perf log files. (Note: A complete trace file should be name as <number>.etl. And the clrrundown file is an intermediate file which should be clean up once the diagnostic tools finished gathering/merging the traces)


Please package your files into a zip file and name the zipped file Feedback-709821.zip.
You can upload the file to workspace:

https://sftasia.one.microsoft.com/choosetransfer.aspx?key=5d606cdd-4289-47af-bd1d-6ab77876dfe7
Password: @tlZ3+cda

Thanks again for your efforts and we look forward to hearing from you.
Posted by MS-Moderator01 on 11/30/2011 at 4:44 AM
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.