Home Dashboard Directory Help
Search

"Disable Database" causes permanent "Initializing..." prompt, constant CPU use, sluggish UI by Martin Ridgers


Status: 

Closed


5
0
Sign in
to vote
Type: Bug
ID: 779199
Opened: 2/14/2013 4:36:00 AM
Access Restriction: Public
1
Workaround(s)
view
1
User(s) can reproduce this bug

Description

When the Intellisense database is disabled and a large solution loaded, Visual Studio will begin displaying an "Initializing..." prompt in the status bar after the "Solution Rescan Interval" period of time has elapsed. Once this happens, VS constantly consumes CPU time, the performance of it's "Find In Files" feature is orders of magnitude slower, and the UI sluggish.

VS Version; 11.0.50272.1 RTMREL
Details
Sign in to post a comment.
Posted by Microsoft on 2/15/2013 at 4:05 PM
Hi Martin,

Thank you for taking the time to provide your feedback. This indeed is a bug in our product. After reviewing your reported issue in the context of all the issues reported to us, we are considering fixing this bug in one of our future releases.

In the meantime, could you please consider accepting this workaround until you get a product release from us with the fix? Prior to setting the "Disable Database" flag to False, set the "Solution Rescan Interval" to 0. This will prevent Visual Studio from rescanning the solution and constantly using CPU.

The issue has been added to our internal database, so it will be closed in Connect. Thank you for helping make Visual Studio a better product!

Sincerely,

Oleg Kharitonov,
Visual C++
Posted by Microsoft on 2/14/2013 at 11:45 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 2/14/2013 at 4:50 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.
Posted by Martin Ridgers on 2/14/2013 at 4:37 AM
Set "Solution Rescan Interval" to the maximum value (5000) to defer the bug for 3.5 days.