The official source of product insight from the Visual Studio Engineering Team
There is now a patch available for this issue in the VS 2010 RC. If you're experiencing frequent crashing when IntelliSense pops up or is dismissed, please download this patch to see whether it resolves the issue. This bug has also been fixed for VS 2010 RTM.
Shortly before the Visual Studio 2010 Release Candidate (RC) was released, the Visual Studio team discovered a significant VS crashing bug on machines using UI Automation (UIA). This bug will only affect a certain group of users, but for those users it renders the IDE very unstable. We’d also like to stress that this issue has already been fixed for VS 2010 RTM.
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 screen reader software, multi-touch drivers, or tablet PCs. Furthermore, the issue applies most commonly to customers using UIA on Windows 7 and Windows Server 2008; impact on prior operating systems should be minimal.
If you are experiencing this issue, you’ll see Visual Studio crashing frequently during rapid typing in the editor while IntelliSense is popping up and/or being dismissed.
There is a patch available for this issue in the VS 2010 RC. We also have a fix for this bug checked in for VS 2010 RTM. You won’t need a 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
I’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!