Find all references freezes VS, takes too long, Escape key doesn't work while VS is frozen - by veeroo

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


5
0
Sign in
to vote
ID 775854 Comments
Status Resolved Workarounds
Type Bug Repros 2
Opened 1/5/2013 12:01:12 AM
Access Restriction Public

Description

We have a solution of about 50 projects (mainly WPF and Class Libraries).
I have discovered, that Find all References on items, that are references almost in every XAML file freezes VS and takes too long.
It's about 30 seconds of lag while searching for about 400 symbol references.
During the lag, there is 'Looking for symbol in XAML files... Press Escape to cancel' status on the status bar.
There are about 120 XAML files in our solution and looking for Find All References on 'Model' in the code behind took about 30 seconds.
Our Model is the DataContext for our View and it derieves from the ViewModelBase. It also implements INotifyPropertyChanged.
Out Views (XAML files) have bindings to the Model.
ESC key during search doesn't work - it doesn't stops searching, VS is totaly frozen ('Visual Studio is busy' popup occurs)
After about 30 seconds there are about 400 results in the Find Symbol Results window.
Sign in to post a comment.
Posted by BrandonCD on 9/2/2015 at 10:55 AM
This is happening to me in VS2015
Posted by Lingling [MSFT] on 10/17/2014 at 4:27 PM
Hi SeanHalliday,

Thanks for reporting the issue to us. We would like to understand the issue you have. Could you send me your steps to reproduct the performance issue, and also could you let me know if you only have this issue on WPF projects or you are using other type of projects?

Thanks,
Lingling
Posted by SeanHalliday on 10/17/2014 at 9:23 AM
This is definitely not fixed in VS 2013 Update 3. It has been frozen for over a minute (time it took to search for this issue, login, and type this!). I am debugging the application at the same time.
Posted by Deon [MSFT] on 4/29/2014 at 12:31 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by Harikrishna [MSFT] on 1/31/2013 at 1:03 PM
Hi Veeroo,
         Visual Studio Update 2 CTP 2 is out. We have made significant investments in improving the performance and reliability of the XAML editor & designer in this update. Do let you know if you can still repro this after the update. Here is the link to the install location http://www.microsoft.com/en-us/download/details.aspx?id=36508
Regards
Harikrishna Menon
Program Manager
Posted by veeroo on 1/9/2013 at 12:55 AM
Thanks for your efforts, I've uploaded dmp file via https://sftus.one.microsoft.com.
Posted by Microsoft on 1/8/2013 at 2:52 AM
Hi veeroo, we want to remind you we need a dmp file. Please send it to us as soon as possible.Thanks.
Posted by Microsoft on 1/7/2013 at 1:51 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting a dmp file. Please submit this information to us within 4 business days. We look forward to hearing from you with this information.
If the dmp file is too large to upload, please follow this
************************************************************
Please zip the file and use "FeedbackID-775854" as prefix of the file name.
************************************************************
You can use the following workspace to upload the file by IE: https://sftus.one.microsoft.com/choosetransfer.aspx?key=9415c965-6590-4d5f-8331-614ff9c106df
Password: Z1_)G37MTk
Thanks again for your efforts and we look forward to hearing from you.
Microsoft Visual Studio Connect Support Team
Posted by Macy [MSFT] on 1/5/2013 at 12:51 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)