Visual Studio 10 -- Your Performance Feedback plus Beta 1

Visual Studio 10 — Your Performance Feedback plus Beta 1 | ASP NET Hosting

Visual Studio 10 — Your Performance Feedback plus Beta 1 | ASP NET Hosting — Thu, 21 May 2009 00:22:47 GMT

PingBack from http://asp-net-hosting.simplynetdev.com/visual-studio-10-your-performance-feedback-plus-beta-1/

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Chris Nahr — Thu, 21 May 2009 09:21:35 GMT

Speaking of the help system -- do you know anything about the long-awaited successor to HTML Help 1.x for standalone applications? Will we get individually deployable MSHelp 2 packages, or something else?

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Chris Nahr — Thu, 21 May 2009 09:30:17 GMT

Never mind, I just saw the announcement for MS Help 3. The team says they are not replacing HTML Help just yet.

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Niall Connaughton — Thu, 21 May 2009 12:23:49 GMT

That copy local issue is a killer, which I'm sure you're aware of. Compilation time is tied almost solely to disk time, and copy local really drags the build speed down. This is especially true in large solutions that are using more projects than NUnit (with more justification hopefully). In the past I've found putting a RAID on a machine has a massive impact on build time. I'm sure I'm not the only one who's found that.

It would be great if there was some way the copy local issue could be addressed or improved. I know you can completely reconfigure your build to have assembly references instead of project references but that brings headaches of its own.

Niall

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Will — Thu, 21 May 2009 12:32:57 GMT

Rico,

How can we ordinary people out here in the cold communicate to the high-ups in MS how ridiculous it looks that, at VS2000 beta1, changing the default tab on the add-ref dialog is still something which we (and that includes you) have to *hope* might happen before RTM?

This is a zero risk, zero localization change, which could have been made 5 years ago in about 5 minutes.

Hell, even making the GAC references load asynchronously would be a couple of hours work and also involve no localisation or doc changes.

I'm sure Raymond Chen or Larry Osterman can dash-off 500 sarcastic words on how we mere mortals are too stupid to appreciate just how hard this is to get done, but I'm afraid from the other side of the looking-glass it's a complete mystery.

If I were you, I'd just go and change the default tab in the source code. It seems unlikely that anyone else in MS will either notice or care.

Ages of silence

Steve Cook's WebLog — Thu, 21 May 2009 13:16:11 GMT

I see I haven't written anything here since February. I've been very busy on two main fronts - lots of

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Tim Dawson — Thu, 21 May 2009 13:34:06 GMT

Your analogy makes little sense. Often when people from Microsoft start trying to redefine the meaning of popular phrases or expectations, it means they're in the process of dropping the ball on something, which makes me worried. Elapsed time is exactly how most people measure, and perceive, UI performance.

Good luck on all the performance work!

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

fowl — Thu, 21 May 2009 14:06:31 GMT

Are you sure hardlinks are the best way to go here? They are indistinguishable in shell from regular files. Could be very confusing to modify one file only to have that propagate to an indeterminate number of others possibly all over the place.

I suppose you can't use symlinks because of their lack of XP support. (vs 2010 runs on XP right?) The shell understands those at least. Ideally you could use some sort of "fast-copy" Copy-On-Write hardlink thing - doesn't exist in windows though :(. Can't you just fix the build process to be able to look directly at the artifacts of other projects?

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

fowl — Thu, 21 May 2009 14:07:50 GMT

Oh and ILMerge should be integrated into the IDE and build system :D

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Marcos — Thu, 21 May 2009 15:40:21 GMT

Rico

In fact the problem that we have with big sulutions is that all the time is getting cunsumed by the disk.

We created an interesed solution with a ram disk, we have a bat that move all our working code to the ram disk and we work from there and do commits from it to avoid lost the changes.

Before we go we copy the code back.

We do all this because we can configure to generate the intermediate /obj stuff in the ram disk only.

There is a way to configure that ?

Best Regards

marcos [at] filehelpers.com

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Marcos — Thu, 21 May 2009 16:05:50 GMT

Rico

I forgot to said that running Visual Studio with the code from the RAM disk Visual Studio is blazing fast for any size of solutions.

So if u want I can share my experiencies with that scenario and maybe I can get a bit of help on how to make Visual Studio to use the RAM to generate the intermediate obj and the Release

Would be so cool to get an option in the project that said "Use volatil intermediate and release" and that project never gets writed to disk

In solutions with 10 projects we only want the output of the last one in the chain, so why write all the intermediate and make the buils pain slow with the Copy Local

If u want more info, contact me to

marcos [at] filehelpers.com

Best Regards

Marcos

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

zzz — Thu, 21 May 2009 19:26:51 GMT

Are you guys saying VS2010 isn't fixing the "HDD is the bottleneck" issue?

I mean if the OS has 5 GB of free physical memory (8 GB total) with VS2010 beta loaded, it's pretty damn obvious that after loading a solution, compiling it should make zero hits to disk! Only hit the disk after compile is finishes and lazily write the data in a background thread.

Unfortunately I just installed VS2010 beta and upon pressing F5 I hear disk access! All the stuff that's needed to compile should be background loading while I'm staring at the editor!

See what's new with Visual Studio product help in the 2010 Beta 1!

Microsoft Help 3.0 Team Blog — Thu, 21 May 2009 22:57:17 GMT

Hey, what's that there? When you hit F1 or go to the Help menu and select Visual Studio Product Documentation,

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Stefan Olson — Fri, 22 May 2009 04:51:51 GMT

Rico,

So far in my day or so of usage with Visual Studio 2010, there a couple of performance problems. The add new item dialog can often take ages (to the extent that I thought the product had died) to appear, also the performance of typing in the new editor is substantially slower than it was Visual Studio 2008.

...Stefan

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

tobi — Fri, 22 May 2009 19:31:59 GMT

On my laptop (2ghz, 2gb ram) scrolling a c# text window is just ridiculously slow. i haven't seen anyone else complain about that so i guess the reason for that is my machine not vs10. vs08 however runs smoothly.

one issue that is independent of the pc vs is running on is text rendering. well.. how can i say politely that ... all text is blurry? i immediately noticed that the solution treeview is still unmanaged because it was sharp. what does that say about wpf text rendering? you cannot ship like this. the wpf team has to make some changes in this regard.

you cannot ship with blurry text.

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Will — Fri, 22 May 2009 19:47:21 GMT

@tobi - the WPF text rendering is apparently going to be fixed for Beta2, not sure when that's due though. The current problem, which is extremely severe in some cases, is disingenuously acknowledged as "Text may appear slightly blurry" in the release notes.

'Slightly' is somewhat of an understatement on this machine, and I'm not one of the anti-anti-aliasing crowd by any means...

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

tobi — Fri, 22 May 2009 20:08:02 GMT

@Will: thanks for the clarification. this makes me sleep easy at night again. but i'm curious: how will it be fixed? if it works for vs then probably all wpf apps can leverage that improvement, right?

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Will — Fri, 22 May 2009 21:42:37 GMT

@tobi - WPF4 is getting a completely new text renderer, which can be told to optimise the placement of characters onto native pixels rather than position them at the theoretically perfect sub-pixel position. (Which is what it does at the moment.)

So yes, this is a benefit which all WPF apps will be able to take advantage of (they may need to enable it specifically though, I'm not sure about that).

Of course, a cynic might think that a major chunk of new functionality like this ought to be in place for something called a 'beta'...

But let's be gracious about that and talk instead about the fantastic and long awaited new help viewer. Ah. Well. Never mind - at least the perf has been inproved hugely. Oh, oops! Well, what about MVC then - that's great. Darn, where is it? The new WPF ribbon is good though. Or so I hear.

Let's face it, this is the CTP which was expected to stop the PDC demo timing-out at the end of last year. It's the {Heros happening}[Here#%] crowd who thought this was a beta.

With any luck, Sinofsky will be along shortly, though...

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

dissapointed — Sat, 23 May 2009 00:08:44 GMT

I'm a long VS fan, going back to VS6

I use VS2005/VS2008 every day at work.

Thats 8-10hrs every working day

Today i installed VS2010 and .. man this thing is sloooow. I can't believe Microsoft dares to release this beta? Nobody who workes daily with VS is going to accept this.

VS2008 was already slow (when compared to VS2005) but VS2010 is simply UN-USABLE

Besides that,

- the text is blurry

- it failed to compile one of my solutions

So please fix it and make it as fast as VS2005

Dissapointed...

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

ricom — Sat, 23 May 2009 03:05:43 GMT

>>If I were you, I'd just go and change the default tab in the source code. It seems unlikely that anyone else in MS will either notice or care.

Sssssshhhh

Not so loud!

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

ricom — Sat, 23 May 2009 03:10:30 GMT

>>Can't you just fix the build process to be able to look directly at the artifacts of other projects?

It's not the build process that's the problem, some solutions really like to have the dependent assemblies be in exactly the right place so that they are discovered/loaded by say an .exe in that directory that doesn't know the assemblies even came from different places.

The build process itself doesn't care :)

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

ricom — Sat, 23 May 2009 03:14:26 GMT

Things every devdiv exec now knows:

1) anti-aliased text can't be the only option

2) the perf of the beta isn't good enough, generally

3) the add references dialog is the bane of humanity

Feel free to write about those things more but at this point you should do it only for recreational purposes :)

Do keep the comments coming, they really help!

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

fowl — Sat, 23 May 2009 03:26:38 GMT

Anti-Aliased text is fine... just don't make up your own.

Cleartype == Awesome.

---

Of course at the end of the proccess everything needs to be where it is supposed to be, but there are many things on disk that are touched/created/copied/etc that aren't used ever again.

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Chris — Sat, 23 May 2009 09:34:53 GMT

It crashes every 10 minutes. Experience in a nutshell

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Szymon — Sat, 23 May 2009 09:44:34 GMT

people complain about vs betas/releases being unstable - well i've had no such problems until this baby.how about Visual Studio Beta Asteriod Edition for a name?

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

tobi — Sat, 23 May 2009 11:27:15 GMT

who cares if the beta is buggy or crashes? those will obviously be fixed in the release and hopefully already in beta 2.

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Will — Sat, 23 May 2009 15:13:56 GMT

"Things every devdiv exec now knows:"

Rico,

You're one of the good guys, please don't turn to the dark side now!

None of these things is a new problem, they've been around for years, and widely complained about, and some of them even have trivial fixes. There is absolutely no evidence of a serious 'exec-level' effort to improve what's already there, despite all the assertions to the contrary.

At the point Soma stops writing about 'pillars' and 'value' and sets his sights on making a folk record, I'll believe there's a chance for a change. VS2010 is going to be Vista - let's just hope that VS2012 is Win7.

And it's not your fault, I do appreciate that.

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Chris — Sun, 24 May 2009 05:04:35 GMT

tobi - a crash then again i'm fine with, but i was being kind when i said ten minutes.Its almost unevaluatable.F# stuff's a bit of a let down as well in this release... although the docs have got better i must admit.

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

zzz — Sun, 24 May 2009 21:05:21 GMT

1) anti-aliased text can't be the only option

Exciting to hear this, I'll take native text over CheatType anyday.

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

zzz — Mon, 25 May 2009 11:24:27 GMT

Stepping through a super simple C# winforms app with F10 is atleast 3 times slower. There's a very noticeable lag in 2010 before it goes to next line.

Earlier I raved about compile perf and fuzzy text.

Since I've read the fuzzy text is getting fixed in Beta 2 or RTM with the text stack replacement, I'd rank the much slower stepping as my current #1 annoying issue in Beta 1.

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

fowl — Mon, 25 May 2009 11:31:42 GMT

Um... native text uses ClearType. People object to the reversion to Apple style "perfection" at the expense of readability that is WPF text rendering v native ClearType.

(Anyway. I'm sure the WPF people know that different people like different styles of text rendering, as long as they provide at least OS native parity they can't be blamed ;)

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Will — Mon, 25 May 2009 13:34:10 GMT

People who are, like me, monumentally disappointed with B1 should have a look at this video:

http://channel9.msdn.com/posts/Charles/Jason-Zander-Perspectives-on-Visual-Studio-2008-and-the-Future-of-VS/

I'm not sure if Jason Zander counts as an 'exec', but he's pretty darn senior wrt VS, and he basically admits that there's a performance crisis which they're now throwing people at (under the guidance of Rico).

It's a great shame that there isn't (yet) the corporate courage to put this sort of stuff into the release notes, but it does feel to me that perf is now being addressed by people who may have enough clout to put some resource on it.

So personally, I shall suspend my churlish whining until B2...

Good luck with your hit-squad, Rico.

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Jens — Mon, 25 May 2009 23:51:33 GMT

Tried opening a vb file with 37000 Lines of code (I know, don't say anything, it's generated code), the memory consumption skyrockets until the VPC is at it limits (1.3 GB), then VS thinks for a minute or 5 and concludes that an error has happened and that it should close.

Opening the same file with VS 2008 is not noticeable in memory consumption.

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Rakesh Patel — Tue, 26 May 2009 10:58:15 GMT

We have 78 projects in solution (include test and setup projects).

VS 2010 crash

1) while opening solution.

2) While compiling single project [I have not tried compiling whole project]

Running on Windows XP SP3, 3 GB RAM, 20 GB HDD Free SPACE, Virtual Memory is configured to manage by System [also tried with 4GB fix allocation].

Here is the Waston Bucket for VS 2010 failure from Event Viewer [if any one want to have look]

EventType clr20r3, P1 devenv.exe, P2 10.0.20506.1, P3 4a0153c5, P4 microsoft.build, P5 4.0.0.0, P6 4a01327b, P7 467, P8 0, P9 onvt03m1rz20jlpuebopcnhakx0ujfrn, P10 NIL.

EventType clr20r3, P1 devenv.exe, P2 10.0.20506.1, P3 4a0153c5, P4 mscorlib, P5 4.0.0.0, P6 4a0125bb, P7 be3, P8 3c, P9 onvt03m1rz20jlpuebopcnhakx0ujfrn, P10 NIL.

EventType clr20r3, P1 devenv.exe, P2 10.0.20506.1, P3 4a0153c5, P4 mscorlib, P5 4.0.0.0, P6 4a0125bb, P7 1467, P8 58, P9 onvt03m1rz20jlpuebopcnhakx0ujfrn, P10 NIL.

EventType clr20r3, P1 devenv.exe, P2 10.0.20506.1, P3 4a0153c5, P4 mscorlib, P5 4.0.0.0, P6 4a0125bb, P7 1ecc, P8 7, P9 system.outofmemoryexception, P10 NIL.

Another exception detail from event viewer

Application: devenv.exe

Framework Version: v4.0.20506

Description: The process was terminated due to an unhandled exception.

Exception Info: Microsoft.Build.Shared.InternalErrorException

Stack:

at Microsoft.Build.BackEnd.RequestBuilder.CancelRequest()

at Microsoft.Build.BackEnd.BuildRequestEntry.Cancel()

at Microsoft.Build.BackEnd.BuildRequestEngine+<>c__DisplayClass12.<DeactivateBuildRequest>b__10(System.Object)

at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)

at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()

at System.Threading.ThreadPoolWorkQueue.Dispatch()

at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

-----------------------------

Application: devenv.exe

Framework Version: v4.0.20506

Description: The process was terminated due to an unhandled exception.

Exception Info: System.OutOfMemoryException

Stack:

at Microsoft.Build.Execution.BuildManager+<>c__DisplayClass9.<ExecuteSubmission>b__7(System.Object)

at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)

at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()

at System.Threading.ThreadPoolWorkQueue.Dispatch()

at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Will — Tue, 26 May 2009 14:49:03 GMT

Rakesh, seems to me you'd be much better filing this sort of thing as a proper bug through the feedback option.

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Keith Patrick — Tue, 26 May 2009 19:34:49 GMT

I'm seeing the lags in the IDE as well. Double-click a file, and everything hangs for 5-10 seconds before anything happens. Ditto for editing text; jut start typing, and at random points it will freeze for another 5 seconds (and honestly, the new color scheme in the IDE combined with this makes it look like the UI is hung trying to finish painting around the windows). On the other hand, I haven't had the IDE crash on me yet, while I get 3-5 crashes a day under VS2008. However, until MS explicitly says they are having a coding initiative around stablizing legacy code, I just don't have confidence that 2010 will be more stable by RTM (the "cycle", as I call it, goes "1. File bug with MS Connect, 2. Wait a week while MS says they are looking into it, 3. MS says to fix will involve architectural changes out of scope for this release, 4. I tell my management, 'sorry, but MS says to wait until some future release.')

On the other hand, I am very glad that MS is finally getting around to focusing on performance in multiple apps...for years it felt like MS was using their security initiative as an excuse for ignoring a growing problem (VS2008 on RTM Vista was absolute HELL for me)

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

bdodson — Wed, 27 May 2009 11:02:12 GMT

I've noticed that changing something in Tools|Options... results in a >10second hang on my computer (font size changes don't seem to do anything either). Not sure what's up with that.

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Sun, 31 May 2009 00:52:24 GMT

Everything is slow on my machine (3.66Ghz Core2 + 8GB ram on x64 Win7):

Here is the main points. The more the stars, the slower it is:

* Starting VS2010 (even on subsequent runs)

*** Opening a Solution

* Opening a file within a solution

** Editing the file

* Compiling C#

** Compiling C++

** Launching the debugger (F5)

**** Debugging (Steps and Steps In are painfully slow) C#

***** Historical debugging

And I get a *lot* of random crashes on various actions. I crash at least 10x a day.

I hope that the data MS is collecting from me participating in the "Customer Feedback Program" includes performance and crashes with a stack mini dump.

This is by far the least stable Beta1 I haver ever tested of VS, and I have been beta testing since VS97.

Good luck Rico, you have your work cut out for you.

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

ricom — Sun, 31 May 2009 11:05:01 GMT

Keep the comments coming, they really help!

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Stephen A. — Mon, 01 Jun 2009 03:52:59 GMT

The new code editor is really, really slow with large files.

For example, VS2008 works acceptably with this file, wheras VS2010 Beta 1 is simply unusable: http://opentk.svn.sourceforge.net/viewvc/opentk/trunk/Source/OpenTK/Graphics/GL/GLDelegates.cs?revision=1803

Interestingly, the VS2010 editor works much better with a 5.5MB file, compared to the VS2008 editor: http://opentk.svn.sourceforge.net/viewvc/opentk/trunk/Source/OpenTK/Graphics/GL/GL.cs?revision=1806

Both files contain parts of auto-generated OpenGL bindings. While this is not a commont use case, it is good to see improvements in this area. It's a little mystifying why the first file performs worse - bug?

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

brads — Tue, 02 Jun 2009 00:30:27 GMT

Hi n,

Your concerns about stepping are my concerns as well. If you turn off historical debugging (in Tools->Options) is your stepping performance still poor?

If you have specific scenarios that seem too slow, it's a good idea to file a bug here:

http://connect.microsoft.com/VisualStudio/content/content.aspx?ContentID=12362

This will allow us to engage more directly and reproduce the issues that you're seeing.

Thanks,

Brad

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Tue, 02 Jun 2009 07:17:36 GMT

Hi brad, turning off historical debugging does help with the debugging speed a bit.

I have filed over 20 bugs so far about VS2010B1, but none specific on performance as I thought that at this stage, poor performance is a known issue.

The historical debugger causes a lot of issues for me, like it steels focus some times and you cant step anymore unless you re-click on the edit..sometimes you have to step twice to make the debugger step once..also the historical debugger somtime just freezes on me, and I cannot click on any of it's items...etc...

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

ricom — Wed, 03 Jun 2009 22:19:30 GMT

Please *do* file your performance bugs, it really helps us to focus on what customers need the most. Even if we already know consider it like a vote.

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

ricom — Wed, 03 Jun 2009 22:28:04 GMT

Stephen A wrote about some editor performance issues. I was able to observe the same problems as Stephen but as an added experiment I tried opening his files as 'foo.txt' rather than .cs files. The editor works fine in those cases.

Looks like the problem is in the language service rather than the editor itself (this happens more than you might think actually)

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Stephen A — Thu, 04 Jun 2009 17:55:28 GMT

I can reproduce these findings both in VS2008 and VS2010: opening as a text file works fine (and VS2010 looks faster than VS2008 in this case).

Performance also picks up after you leave the whole solution open for some time. The language process presumably settles down and you can browse either of these files without issue.

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Rico Mariani — Fri, 05 Jun 2009 23:15:51 GMT

That test case has surfaced several things I didn't like. It's getting attention :)

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Dan Moseley — Tue, 09 Jun 2009 02:40:57 GMT

@Rakesh Patel

I've gotten other reports through Watson (uploaded crash dumps) of this OutOfMemoryException but to make progress I need a full heap dump which I don't have yet. If you can make one at the point of failure, please let me know at msbuild@microsoft.com. Otherwise, I'll wait for one to get uploaded by another customer through the watson system.

Thanks

Dan (msbuild team)

re: Visual Studio 10 -- Your Performance Feedback plus Beta 1

Joren — Mon, 15 Jun 2009 04:16:04 GMT

There is a horrible performance bug in IntelliSense in the VS2010 Beta. It can slow to a crawl.

The following reproduction works invariably on my machine.

1. Open a C# project.

2. Wait for the IntelliSense documentation cache to construct.

3. In a method body, type "System.Linq.Expressions.Expression.Call(". (popping up IntelliSense for the Call overloads)

3. Press and hold the up key

4. Watch IntelliSense grow *progressively* slower while it browses through the overloads.

Interestingly, browsing with the down key instead of the up key only does not cause any slowdowns.

Unfortunately, once you do the repro, method overload browsing is slowed down for all methods, not just the method that caused the slowdown. Closing the solution seems to reset the problem.

Fortunately, not all methods can cause this slowdown. I haven't been able to pin down why some methods would have problems and others not.

But at least it doesn't seem to matter that the number of overloads for the affected methods (14 for Expresson.Call) is large: On the one hand, Console.WriteLine has more overloads (19) than Expression.Call, but it will not cause the slowdown. On the other hand, Enumerable.SelectMany has a lot less overloads (4), but will cause the slowdown.

I hope you're able to reproduce the bug as easily as I am.