Second patch now available for IntelliSense crashes in VS 2010 RC

Second patch now available for IntelliSense crashes in VS 2010 RC

Rate This
  • Comments 44

We recently blogged about a crashing bug in the Visual Studio 2010 Release Candidate (RC) on machines using UI Automation (UIA).  We’ve since discovered that there are actually two bugs, both of which will only affect a certain group of users but will cause the IDE to be very unstable for those users.  Both of these issues now have patches available for the RC and have already been fixed for VS 2010 RTM.

Who is affected?

Both bugs affect the same group of users.  Only machines with the Visual Studio 2010 RC and an application or device actively using UI Automation 3.0 APIs are affected.  This includes but may not be limited to RC users who are using touch displays, tablet PCs, screen reader software, and some 3rd-party applications.

What are the symptoms?

Both bugs cause Visual Studio to be quite unstable.  Bug #1 causes frequent crashing during rapid typing in the editor while IntelliSense is popping up and/or being dismissed.  Bug #2 causes somewhat less frequent crashing during tooltip invocation, most commonly when hovering over an identifier to view a QuickInfo tooltip.

How can I fix these crashes?

There are two separate patches available for these issues in the VS 2010 RC, and we’d encourage RC users to download and install them both.  We also have fixes for both bugs checked in for VS 2010 RTM.  You won’t need a patch or workaround for the final release, and you’ll be able to use the RTM build on machines with UIA without experiencing these crashes.

If you have any questions about this issue, please feel free to post in the comments below.  If you’re experiencing crashes without UIA or in scenarios without IntelliSense, the root cause is likely different, so we’d encourage you to collect a crash dump if possible and file a Connect bug so we can investigate.

Brittany Behrens
Program Manager, Visual Studio Editor Team

clip_image002I’m Brittany, a Program Manager on the Visual Studio Editor team.  Some of you may recognize me from Connect bugs or as the main voice of @VSEditor on Twitter, and I’m responsible for a variety of Editor features.  I love hearing from customers, so please let me know what you think!

Leave a Comment
  • Please add 6 and 2 and type the answer here:
  • Post
  • oh yearh

  • Hi, I would like to know if we should install these two patches also on normal VM Windows 7 machines or only if we plan to use a UIA technology.

    Thank you

  • @raffaeu:

    If you're not seeing frequent IntelliSense crashes, you probably don't need these two patches.  That said, they're safe to install on any machine with the VS 2010 RC; if UIA isn't active, neither the crashing code path nor the hotfix code should be hit, so you should see no change in behavior.

  • Thank you so much for the clarification

  • Hi, I have installed the above patches but still have this problem.  My computer is not a tablet PC, etc.  I am running on Windows XP Professional 64-bit.  Before applying the patches, when Intellisense was popping, it would take a good 15 to 30 seconds to appear and it would randomly crash as well.  After the patches were applied, it doesn't seem to crash, but the CPU still maxes out, there is a 15 to 30 second delay and then intellisense pops out.

    Is this a bug only running on XP 64-bit version?  Anyone else still has the problem even after applying the pacthes and running on 64-bit?

    Thank you!

    -- Nima

  • *** UPDATE ***

    Further to my message above, I have been able to resolve the problem on my Windows XP Pro x64 (it seems). I am not sure exactly what fixed it, but these are the steps I have taken.  Hopefully it'll help someone:

    1. Installed the TWO patches released so far.  After this, it wouldn't crash, but the speed was the same.  Very slow, about 15 to 30 seconds for intellisense to appear.

    2. I read somewhere than Windows Automation API should be updated to latest version 3.0.  I went to: http://support.microsoft.com/kb/971513 and there wasn't a version for Windows XP Professional x64, but I went ahead and downloaded and installed

    "Update for Windows Server 2003, x64-based versions"

    anyways since XP x64 uses the same core as Windows Server 2003 as far as I understand.

    3. I should have probably tested things after the above, but I didn't and ran Windows Update and installed all critical updates to date as well.

    After a reboot, intellisense is now working as it should and is almost instanenous.

    Hope this helps.

    -- Nima

  • Hi,

    Thanks for the patch - VS2010 is a hell of a lot more stable now. BUT I'm now getting a strange error where the mouse pointer is behaving strangely. Things like;

    - the pointer changes to a text selection pointer over menus and the toolbar. I then can't click on menus/icons

    - I can't select any text in the code editor (though the pointer is correct)

    I'm running Windows 7 x64 with a Wacom tablet.

    Thanks,

    Paul

  • How long does this take? I'm running XP SP3 and it's taking over an hour. No disk activity, and CPU's flat as well. It's hung about 3/4 complete.

  • @Paul:

    What you're describing sounds like a bug, but it's almost certainly unrelated to this patch.  Could you file a Connect bug (http://connect.microsoft.com/VisualStudio) about this?  It would be especially helpful if you could record a short video of the problem in action and attach it to the Connect report.  If you don't already have video capture software, a free Microsoft tool called Community Clips makes this fairly quick and easy:  http://www.officelabs.com/projects/communityclips/Pages/Default.aspx/.  Feel free to post the bug number here so we can route it to the right team more quickly.

    @Mike:

    Sorry, how long does what take - patch installation?  It should be quite quick (nowhere near an hour).  If the installation is hung, could you kill the process and try again?

    - Brittany

  • I am having the same problem with the patch hanging on a windows 7 x64 machine.

  • I am having the same problem with the XAML designer failing. I am using the new VS2010 full production version. When I installed SL 4 it broke VS2010 SL XAML designer. I have invested over six hours trying to resolve this issue. If I cannot find a solution in about two more hours I will remove SL4 indefinitely. I have to get my work done!

    System.NullReferenceException

    Object reference not set to an instance of an object.

      at Microsoft.Expression.Platform.Silverlight.SilverlightDomainManager.CreateDomainCore()

  • @Joe:

    This sounds like an unrelated issue and one that would be better addressed by the XAML designer team.  Your best bet is to post in their VS 2010 RTM forum at http://social.msdn.microsoft.com/Forums/en-US/vswpfdesigner/threads.

    - Brittany

  • @Nima

    Thanks for the post!  I hadn't realized you could use the Server 2003 patch on XP 64-bit, but I installed it, and now my Visual Studio is working like it's supposed to.

  • Hi,

    I'm a student and i use the visual studio express 2010 ,downloaded from a microsoft website.The intellisense never worked.The patches also fail to install.

    i got this error:

    KB980610 does not apply, or is blocked by another condition on your computer.

    Is that because i dont have a professional version of vs2010?

  • Yes,  express does not include intellisense.  Also, in VS 2010, intellisense will not work if you are creating a windows form application using a CLR file.

Page 1 of 3 (44 items) 123