Search

Code Editor is too slow! by volatiless

Closed
as External Help for as External

13
0
Sign in
to vote
Type: Bug
ID: 527907
Opened: 1/28/2010 10:03:51 AM
Access Restriction: Public
1
Workaround(s)
10
User(s) can reproduce this bug
Not possible to write code. Code editor is too slow.

Give my vs2008 code editor back with normal fonts (OMG)!
Details (expand)

Product Language

English

Version

Visual Studio 2010 Beta 2

Operating System

Windows 7

Operating System Language

English

Steps to Reproduce

Insert
"value1", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value", "value""value", "value", "value", "value", "value", "value", "value", "value""value", "value", "value", "value", "value", "value", "value", "value""value", "value", "value", "value", "value", "value", "value", "value""value", "value", "value", "value", "value", "value", "value", "value""value", "value", "value", "value", "value", "value", "value", "value""value", "value", "value", "value", "value", "value", "value", "value""value", "value", "value", "value", "value", "value", "value", "value""value", "value", "value", "value", "value", "value", "value", "value""value", "value", "value", "value", "value", "value", "value", "value""value", "value", "value", "value", "value", "value", "value", "value""value", "value", "value", "value", "value", "value", "value", "value""value", "value", "value", "value", "value", "value", "value", "value"

too code editor and try to insert escape chars before each ".

Actual Results

VS freezes for few minutes.

Expected Results

VS2008 perfomance is expected.
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey. [Details]

 

File Attachments
0 attachments
Sign in to post a comment.
Posted by nathalav on 9/6/2011 at 12:23 PM
I am experiencing this since i installed Visual Studio 2010
I have latest version Microsoft Visual Studio 2010 and updates
My operating system is Windows XP 32 bits 3 gig memory
I also installed the workaround http://support.microsoft.com/kb/971513/
But I am still expriencing this issue
Posted by Ruud v A on 5/30/2010 at 1:24 PM
I experience the same problem with intellisense. This is only the case with C++ projects, C# is fast. It just takes too long to resolve the symbols typed, after typing a . or -> or ::, it can take up to twenty seconds to come up with the list of suggestions. Sometimes it pops up immediately, but most of the time not. Also when I type a ., then wait till the list pops up, then remove the dot and type it again, it is going to examine everything again, so I have to wait a very long time again. This basically makes intellisense unusable in Visual Studio 2010 when working with C++.

I am using the latest version of Visual Studio 2010:

Version 10.0.30319.1 RTMRel
Microsoft .NET Framework
Version 4.0.30319 RTMRel
Installed Version: Ultimate
Microsoft Visual C++ 2010
Hotfix for Microsoft Visual Studio 2010 Ultimate - ENU (KB982218) KB982218

Windows 7 Home Premium 64-bit.
Posted by .NET Master on 3/15/2010 at 5:16 AM
As an added note, I have discovered that if I do a Find In Files search, it immediately triggers the high cpu utilization, which continues after the search completes, and requires that I restart VS2010 to do any further work.
Posted by .NET Master on 3/15/2010 at 2:54 AM
I am having the same problem on VS 2010 RC running on Windows 7 Ultimate 64-bit (12GB memory, 3GHZ processor), with the intellisense patches applied. I also do not have touch or tablet features enabled.

The devenv.exe process goes to 50% cpu utilization on an 8 core (dual 4-core processors) machine, and stays there forever.

Also, if I just leave VS2010 running, the memory utilization goes up. Went from 868MB to 2.9GB overnight, while just sitting minimized!
Posted by bdejong_cree on 3/10/2010 at 10:28 AM
I applied the http://support.microsoft.com/kb/971513/ fix to my system and the Intelisense is working perfect, even with VS2008 IDE open at the same time. This fix appears to work.

Using
Windows XP SP3 x86
VS2010 RC
VS2008 SP1
Posted by Mike Andrews on 2/27/2010 at 5:20 AM
I'm experiencing this same problem as well. Just like hvjackson, I get a very slow unusable editor. I'm not using Windows XP, but Vista SP1. I'm not using a tablet or touch-enabled pc either.

I did install the hotfix to see if that would correct the problem regardless, but to no avail. I was hoping to start using VS 2010 RC, but it's unusable in its current state.
Posted by Microsoft on 2/15/2010 at 3:05 PM
We have discovered that this is related to WPF performance issues on tablet and touch enabled machines. This is due to a lack of UIA virtualization with UIA 2.0. Win7 ships with UIA 3.0 which enables virtualization but Vista/Server2x8 and XP do not. Our intellisense code relies on virtualized lists so that we don’t have to load all the items in the statement completion list when we bring it up. With UIA 2.0’s lack of virtualization, this results in us loading all the statement completion list items before we bring up statement completion, which results in the statement completion popup lag and typing perf issues.

Please try the following update and let us know whether Editor performance got any better or not. You can reach me at selmai at Microsoft.com.

The solution is to update from UAI API 2.0 to 3.0, you can find the packages : http://support.microsoft.com/kb/971513/ . Note that the CodeEditor team right now is working on a patch to fix the crash that a user will experience with intellisense on UIA 3.0 (please see blog post on this http://blogs.msdn.com/visualstudio/archive/2010/02/09/intellisense-crash-in-ui-automation.aspx).

Note that UIA 3.0 APIs is not supported for XP x64 bit OS, hence you can overcome this issue by uninstalling tablet driver and software.

Thank you!
Selma Ikiz
VS Platform Team
http://blogs.msdn.com/visualstudio
Posted by Microsoft on 2/11/2010 at 9:42 AM
Thank you for taking time and giving us feedback!
I am on a separate email thread with Hvjackson. We believe that this is an OS specific issue and reproes only on XP (Mikecvelide’s comment also supports thi). Trvenkat, could you please also let us know your operating system? In fact, it would be easier for us if you can you 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). This will give us more information about your OS/processor speed/etc.
You can reach me at selmai at Microsoft.com.
Thank you!
Selma Ikiz
VS Platform Team
http://blogs.msdn.com/visualstudio
Posted by trvenkat on 2/11/2010 at 2:20 AM
Same issue for me. I have been unable to work from the time I installed VS2010 Beta 1 and was eagerly waiting for RC. I installed it today, and very disappointed to see nothing improved. I spent half day and could not write any code.

Scrolling is totally slow, Switching between windows almost dies, Writing code is soo slow, I feel like going back to VS2008.

Any one, pleeaseeeeeeee help :(
Posted by hvjackson on 2/10/2010 at 10:06 AM
Just a bit of follow-up... some C# files are much worse about this than others, I'm not sure why.

It DOESN'T appear to be related to any of the following:
- Number of "using" statements
- Targeting .NET 3.5 or .NET 4
- Upgraded VS2008 solution or native VS2010 solution

However, disabling Intellisense does seem to fix the problem (but of course negates one of the primary benefits of using an IDE).
Posted by mikecvelide on 2/10/2010 at 8:46 AM
I'm dealing with the same problem and it really is unworkable. For me it's more like every few seconds, as in within one line of code I might experience a couple of these hangs. I can either just keep typing and let the editor (eventually) catch up or stop and wait for it. Either is useless. I've reset all my settings to default C# and I have no addons loaded (fresh install of VS2010 RC). I'm running on XP64 w/ dual core 2.66GHz CPU & 4 GB of RAM. This solution was upgraded from a VS 2008 solution where it ran perfectly. One of my coworkers is working on the same source code using an identical system. He experiences this issue as well, but less frequently.
Posted by hvjackson on 2/9/2010 at 1:44 PM
Actually, it's so bad I just checked to make sure I hadn't accidentally downloaded an old beta. But nope, it's the RC...
Posted by hvjackson on 2/9/2010 at 1:39 PM
I'm experiencing sporadic extreme slowdowns with the new VS2010 RC. Every couple minutes, as I try to type something, VS completely hangs for maybe 15 seconds. It looks like Intellisense is churning or something.

I've been keeping an eye on Windows Task Manager, and I see one core pegged for the duration of the hang, and the "devenv.exe" process is at 50%.
Posted by Microsoft on 2/2/2010 at 3:24 PM
Thank you for taking time and giving us feedback!
Since Beta2, we have improved VS2010 quite a bit and Brian Harry is blogging about these improvements here : http://blogs.msdn.com/bharry/archive/2010/01/24/state-of-vs-2010-performance.aspx . Later next week, a public version with most of these improvements will be available(http://blogs.msdn.com/somasegar/archive/2009/12/17/visual-studio-2010-and-net-framework-4-beta-period-extended.aspx). If you do not want to wait until then to try out our changes, please reach me at selmai at Microsoft.com.
I am resolving this as fixed, please feel free to re-activate this if you think issue is still reproducing with never versions.
Thanks again for your feedback,
Selma Ikiz
VS Platform Team
http://blogs.msdn.com/visualstudio
Posted by Microsoft on 1/28/2010 at 9:51 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.

Thank you
Sign in to post a workaround.
Posted by Selma Ikiz - MSFT on 2/15/2010 at 3:08 PM
Please try the following update and let us know whether Editor performance got any better or not. You can reach me at selmai at Microsoft.com.

The solution is to update from UAI API 2.0 to 3.0, you can find the packages : http://support.microsoft.com/kb/971513/ . Note that the CodeEditor team right now is working on a patch to fix the crash that a user will experience with intellisense on UIA 3.0 (please see blog post on this http://blogs.msdn.com/visualstudio/archive/2010/02/09/intellisense-crash-in-ui-automation.aspx).

Note that UIA 3.0 APIs is not supported for XP x64 bit OS, hence you can overcome this issue by uninstalling tablet driver and software.