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
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!
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.
I am having a problem with 2010 Express where the IDE crashes and appears to relate to intellisense. If I type "Inpu" and select "InputBox" from the options offered and press the "open bracket" the IDE returns "Microsoft VB 2010 has encountered a problem and needs to close" then sometimes it just closes and other it returns another message "Microsoft VB 2010 Express has stopped working" If I cut and paste the InputBox command there are no problems, its only when I hit the "Open Bracket". What makes this even weirder is I have been using this install of IDE for months without a problem. I work on two machines, a laptop at home and a desktop at work and pass the developing application to each via Dropbox.com. Any clues??
@Brad
Could you attach an instance of VS to VS before making it crash, enable mixed mode debugging, turn off 'Just My Code' and point it at the public Microsoft symbol servers? If you then repro the crash it should break into the debugging VS instance with information and you can grab a callstack. You can send it to me at rmolden AT microsoft.com and I can take a look to see if anything obvious jumps out at me.
Have you installed any new extensions lately?
Ryan
Hello ryan,
Thank you for the response, I'm afraid my knowledge is not up to this level. How do I attach an instance of of VS to VS? I can turn off "Enable Just My Code" in options (currently turned off)and have also ticked Microsoft Symbol Servers.
I haven't installed any new extensions lately.
Brad
@Brad
You should be able to launch two instances of VS. Open a project in one so it is easy to identify in the latter steps. In the other VS instance go to Tools->Attach To Process (I believe this is available in the Express SKUs, if not we would have to use WinDBG, which is…a little less user friendly :)). Select devenv.exe from the list of listed processes (make sure it is the one whose Title field is showing the project you opened in the other VS instance), also make sure that the Attach To combo above the list of processes is set to "Managed (v4.0) code, Native code". That should then attach to the other instance of VS, if you switch over to it now and reproduce the crash it should then break into the instance that is debugging and present you with the exception information and a callstack.
Ryan
Ryan,
Wouldn't you know there is no "Attach To Process" on the Tools Menu. Should I download WinDBG?
Brad
@Brad
Sure, definetly less user friendly, but here are the steps you should follow
1: Launch VS as before and load a project.
2: Launch WinDBG.
3: In WinDBG choose File->Attach to a process…
4: Find Devenv.exe in the list shown in the dialog that comes up.
5: Choose Ok (it will say something like 'save information for workspace', you can say no to that)
6: Once it has attached go to File->Symbol File Path and enter this into the pop-up dialog (without the quotes) "SRV*msdl.microsoft.com/…/symbols"
7: Click OK
8: Go back to VS.
9: Make it crash.
10: Go back to Windbg.
11: Type ".loadby sos clr" into the typing area at the bottom of the screen and hit enter (again without the quotes).
12: type "~0s" into the typing area and hit enter (again, no quotes)
13: type "k" into the typing area (again, no quotes) and hit enter.
That should give you a callstack dumped to the window above where you have been typing, hopefully it will have nice resolved symbols and such (due to step 6), if you could post that here or send it to my mail I can see if anything obvious is wrong or if there is a known bug you are seeing.
Ryan
And the string in step 6 which the blog software turned into a hyperlink should be SRV* followed by HTTP:// followed by msdl.microsoft.com/download/symbols. Hopefully my spacing above is enough to prevent the blog software from once again turning it into a hyperlink 🙂
Ryan
Thanks Ryan,
It looks like a big download (300MB) so will try as you say and let you know what happens.
Thanks Again
Brad
Are you getting it from here: http://www.microsoft.com/…/confirmation.aspx
I think you can unselect everything except the 'debugging tools', you just need WinDBG…not sure if there is an easier way to get it but you don't need all the SDK stuff that they seem to be bundling it with.
Ryan
That page I linked has these instructions for 'slimming down' the download (You probably want the 'Debugging Tools' under Common Utilities, the x86 version), make sure to uncheck everything else like they say to avoid downloading stuff you don't need:
The Debugging Tools are listed in two places on the Installation Options screen in the Windows SDK Setup Wizard:
Select the Debugging Tools option under the Common Utilities if you want the x86 version of the Debugging Tools and you are installing on an x86 computer. This option automatically detects the CPU architecture of the computer on which you are installing the tools and it is the fastest method of installing the tools.
Select the Debugging Tools option under the Redistributable Packages to download all three versions of the Debugging Tools (x86, x64, Itanium).
After you select the appropriate Debugging Tools option as described above, clear the check boxes for the other options so that you do not install unnecessary items. The Common Utilities option downloads the Debugging Tools into a Debugging Tools for Windows folder under your Program Files folder. The Redistributable Packages option downloads the Debugging Tools to C:Program FilesMicrosoft SDKsWindowsv7.1RedistDebugging Tools for Windows.
Ryan,
Have downloaded WinDBG and launched it, however there is no Process named Devenv.exe
Brad
Hmmm, what is the name of the VB Express executable? If you look at the shortcut link what is it pointing at? That is the name of the executable we are looking for. It might be something like VBExpress.exe or something.
Ryan
Attached to process: vbExpress.exe and the following was displayed in the window:
0:043> ~0s
eax=00694248 ebx=0029f118 ecx=00694248 edx=00912f88 esi=00000001 edi=00000000
eip=77a96344 esp=0029f0c8 ebp=0029f164 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
ntdll!KiFastSystemCallRet:
77a96344 c3 ret
0:000> k
ChildEBP RetAddr
0029f0c4 77a95cac ntdll!KiFastSystemCallRet
0029f0c8 75c76872 ntdll!ZwWaitForMultipleObjects+0xc
0029f164 76bcf14a KERNELBASE!WaitForMultipleObjectsEx+0x100
0029f1ac 76c790be kernel32!WaitForMultipleObjectsExImplementation+0xe0
0029f200 65e0dc17 USER32!RealMsgWaitForMultipleObjectsEx+0x13c
0029f250 65e130cb msenv!CMsoCMHandler::EnvironmentMsgLoop+0x139
0029f290 65e12ffc msenv!CMsoCMHandler::FPushMessageLoop+0x156
0029f2b4 65e12f5d msenv!SCM::FPushMessageLoop+0xab
0029f2d0 65e12f2a msenv!SCM_MsoCompMgr::FPushMessageLoop+0x2a
0029f2f0 65e12e6c msenv!CMsoComponent::PushMsgLoop+0x28
0029f388 65d2db92 msenv!VStudioMainLogged+0x553
0029f3b4 00fe8fd0 msenv!VStudioMain+0xbc
0029f3ec 00fe3277 vbexpress!util_CallVsMain+0xfd
0029f6d8 00fe46cc vbexpress!CVBExpressId::Run+0x8d9
0029f708 00ffd01d vbexpress!WinMain+0x9c
0029f79c 76bd1194 vbexpress!operator new[]+0x1e1
0029f7a8 77aab429 kernel32!BaseThreadInitThunk+0xe
0029f7e8 77aab3fc ntdll!__RtlUserThreadStart+0x70
0029f800 00000000 ntdll!_RtlUserThreadStart+0x1b
Does this mean anything to you??
Brad
That is just the process waiting for messages, if you hit F5 in Windbg and then switch back to VB Express and make it crash then go back to WinDBG and do the ~0s, k it would probably be more interesting. Or kp (to also show function arguments).
Ryan
Ryan,
Did as you said
(9fc.1238): C++ EH exception – code e06d7363 (first chance)
(9fc.1238): CLR exception – code e0434352 (first chance)
(9fc.1238): CLR exception – code e0434352 (!!! second chance !!!)
eax=0029c3ec ebx=00000005 ecx=00000005 edx=00000000 esi=0029c498 edi=00402258
eip=75c79617 esp=0029c3ec ebp=0029c43c iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
KERNELBASE!RaiseException+0x58:
75c79617 c9 leave
0:000> ~0
. 0 Id: 9fc.1238 Suspend: 1 Teb: 7ffdf000 Unfrozen
Start: vbexpress!WinMainCRTStartup (00ffd16a)
Priority: 0 Priority class: 32 Affinity: f
0:000> kp
ChildEBP RetAddr
0029c43c 656dac08 KERNELBASE!RaiseException+0x58
0029c4cc 6574ab0b clr!RaiseTheExceptionInternalOnly+0x276
0029c508 65908e1e clr!UnwindAndContinueRethrowHelperAfterCatch+0x60
*** WARNING: Unable to verify checksum for C:windowsassemblyNativeImages_v4.0.30319_32PresentationCore7a1eeb425f9318f432afead4b2da965aPresentationCore.ni.dll
0029c5a4 624db3bd clr!JIT_RngChkFail+0xde
0029c5ec 61d9ba06 PresentationCore_ni+0x8fb3bd
0029c668 61d9b5ae PresentationCore_ni+0x1bba06
0029c6e8 61d9b26f PresentationCore_ni+0x1bb5ae
0029c738 61d9a30b PresentationCore_ni+0x1bb26f
0029c7c0 61d99c71 PresentationCore_ni+0x1ba30b
0029c7ec 61d99bd2 PresentationCore_ni+0x1b9c71
*** WARNING: Unable to verify checksum for C:windowsassemblyNativeImages_v4.0.30319_32PresentationFramewo#8357ade60159c25ee88db0aab8686e6dPresentationFramework.ni.dll
0029c81c 60deb750 PresentationCore_ni+0x1b9bd2
0029c994 60dc475a PresentationFramework_ni+0x2eb750
0029cba0 61d873c3 PresentationFramework_ni+0x2c475a
0029cc24 60dfa8d2 PresentationCore_ni+0x1a73c3
0029cc78 60df9dc5 PresentationFramework_ni+0x2fa8d2
0029cd10 60df90eb PresentationFramework_ni+0x2f9dc5
0029cdd8 60dc475a PresentationFramework_ni+0x2f90eb
0029cfe4 61d873c3 PresentationFramework_ni+0x2c475a
0029d068 60dfa8d2 PresentationCore_ni+0x1a73c3
0029d0bc 60df9dc5 PresentationFramework_ni+0x2fa8d2
0029d154 60df90eb PresentationFramework_ni+0x2f9dc5
0029d21c 60dc475a PresentationFramework_ni+0x2f90eb
0029d428 61d873c3 PresentationFramework_ni+0x2c475a
0029d4ac 60dfac5b PresentationCore_ni+0x1a73c3
0029d4e4 60dfdc20 PresentationFramework_ni+0x2fac5b
0029d4fc 60dc475a PresentationFramework_ni+0x2fdc20
0029d708 61d873c3 PresentationFramework_ni+0x2c475a
0029d78c 60ded65f PresentationCore_ni+0x1a73c3
0029d864 60dc475a PresentationFramework_ni+0x2ed65f
0029da70 61d873c3 PresentationFramework_ni+0x2c475a
0029daf4 60dfaa7e PresentationCore_ni+0x1a73c3
0029db3c 60dc475a PresentationFramework_ni+0x2faa7e
0029dd48 61d873c3 PresentationFramework_ni+0x2c475a
0029ddcc 60df8dbc PresentationCore_ni+0x1a73c3
0029de8c 60dc475a PresentationFramework_ni+0x2f8dbc
0029e098 61d873c3 PresentationFramework_ni+0x2c475a
*** WARNING: Unable to verify checksum for C:windowsassemblyNativeImages_v4.0.30319_32Microsoft.VisualStu# ae881ae2f569623ae0b15ace2014e6fMicrosoft.VisualStudio.Platform.VSEditor.ni.dll
0029e11c 5d0f13a7 PresentationCore_ni+0x1a73c3
0029e154 5d0f0bbe Microsoft_VisualStudio_Platform_VSEditor_ni+0x1413a7
0029e8a0 5d0ef876 Microsoft_VisualStudio_Platform_VSEditor_ni+0x140bbe
0029e8bc 5d10e518 Microsoft_VisualStudio_Platform_VSEditor_ni+0x13f876
0029e904 5d10e47c Microsoft_VisualStudio_Platform_VSEditor_ni+0x15e518
*** WARNING: Unable to verify checksum for C:windowsassemblyNativeImages_v4.0.30319_32WindowsBasef1f3a74eb37b27b7d05b8ffa941f8473WindowsBase.ni.dll
0029e920 6271fac2 Microsoft_VisualStudio_Platform_VSEditor_ni+0x15e47c
0029e960 627229b5 WindowsBase_ni+0xafac2
0029e9ac 62722918 WindowsBase_ni+0xb29b5
0029e9c4 656521db WindowsBase_ni+0xb2918
0029e9d4 65674a2a clr!CallDescrWorker+0x33
0029ea50 65674bcc clr!CallDescrWorkerWithHandler+0x8e
0029eb8c 65674c01 clr!MethodDesc::CallDescr+0x194
0029eba8 65674c21 clr!MethodDesc::CallTargetWorker+0x21
0029ebc0 656ef5f8 clr!MethodDescCallSite::Call+0x1c
0029eda4 656ef74f clr!ExecuteCodeWithGuaranteedCleanupHelper+0xbb
*** WARNING: Unable to verify checksum for C:windowsassemblyNativeImages_v4.0.30319_32mscorlib4ff1f12a08d455f195ba996fe77497c6mscorlib.ni.dll
0029ee50 64ab4cba clr!ReflectionInvocation::ExecuteCodeWithGuaranteedCleanup+0x138
0029ee88 64ab7f34 mscorlib_ni+0x234cba
0029eea8 62722848 mscorlib_ni+0x237f34
0029eee8 6271e57e WindowsBase_ni+0xb2848
0029ef2c 6271e70f WindowsBase_ni+0xae57e
0029ef6c 6271fdb6 WindowsBase_ni+0xae70f
0029efb8 6271fce5 WindowsBase_ni+0xafdb6
0029efd8 6271fb93 WindowsBase_ni+0xafce5
0029eff0 6271fac2 WindowsBase_ni+0xafb93
0029f030 6271e050 WindowsBase_ni+0xafac2
0029f074 6271f5e0 WindowsBase_ni+0xae050
0029f0f0 76c786ef WindowsBase_ni+0xaf5e0
0029f11c 76c78876 USER32!InternalCallWinProc+0x23
0029f194 76c789b5 USER32!UserCallWinProcCheckWow+0x14b
0029f1f4 76c78e9c USER32!DispatchMessageWorker+0x35e
0029f204 65e0d42b USER32!DispatchMessageW+0xf
0029f214 65e0d521 msenv!ProcessMessage+0x69
0029f250 65e130cb msenv!CMsoCMHandler::EnvironmentMsgLoop+0xd8
0029f290 65e12ffc msenv!CMsoCMHandler::FPushMessageLoop+0x156
0029f2b4 65e12f5d msenv!SCM::FPushMessageLoop+0xab
0029f2d0 65e12f2a msenv!SCM_MsoCompMgr::FPushMessageLoop+0x2a
0029f2f0 65e12e6c msenv!CMsoComponent::PushMsgLoop+0x28
0029f388 65d2db92 msenv!VStudioMainLogged+0x553
0029f3b4 00fe8fd0 msenv!VStudioMain+0xbc
0029f3ec 00fe3277 vbexpress!util_CallVsMain+0xfd
0029f6d8 00fe46cc vbexpress!CVBExpressId::Run+0x8d9
0029f708 00ffd01d vbexpress!WinMain+0x9c
0029f79c 76bd1194 vbexpress!operator new[]+0x1e1
0029f7a8 77aab429 kernel32!BaseThreadInitThunk+0xe
0029f7e8 77aab3fc ntdll!__RtlUserThreadStart+0x70
0029f800 00000000 ntdll!_RtlUserThreadStart+0x1b
Brad
Can you do a !PrintException? You did a .loadby sos clr right? There is a managed exception, but the info above doesn't help, unfortunately. Did you set up the SymbolPath? It doesn't look like the symbols are resolved.
Ryan
Started from the beginning and followed instructions:
0:000> .loadby sos clr
0:000> ~0s
eax=0026c47c ebx=00000005 ecx=00000005 edx=00000000 esi=0026c528 edi=00398aa8
eip=75c79617 esp=0026c47c ebp=0026c4cc iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
KERNELBASE!RaiseException+0x58:
75c79617 c9 leave
0:000> kp
ChildEBP RetAddr
0026c4cc 6555ac08 KERNELBASE!RaiseException+0x58
0026c55c 655cab0b clr!RaiseTheExceptionInternalOnly+0x276
0026c598 65788e1e clr!UnwindAndContinueRethrowHelperAfterCatch+0x60
*** WARNING: Unable to verify checksum for C:windowsassemblyNativeImages_v4.0.30319_32PresentationCore7a1eeb425f9318f432afead4b2da965aPresentationCore.ni.dll
0026c634 6034b3bd clr!JIT_RngChkFail+0xde
0026c67c 5fc0ba06 PresentationCore_ni+0x8fb3bd
0026c6f8 5fc0b5ae PresentationCore_ni+0x1bba06
0026c778 5fc0b26f PresentationCore_ni+0x1bb5ae
0026c7c8 5fc0a30b PresentationCore_ni+0x1bb26f
0026c850 5fc09c71 PresentationCore_ni+0x1ba30b
0026c87c 5fc09bd2 PresentationCore_ni+0x1b9c71
*** WARNING: Unable to verify checksum for C:windowsassemblyNativeImages_v4.0.30319_32PresentationFramewo#8357ade60159c25ee88db0aab8686e6dPresentationFramework.ni.dll
0026c8ac 5819b750 PresentationCore_ni+0x1b9bd2
0026ca24 5817475a PresentationFramework_ni+0x2eb750
0026cc30 5fbf73c3 PresentationFramework_ni+0x2c475a
0026ccb4 581aa8d2 PresentationCore_ni+0x1a73c3
0026cd08 581a9dc5 PresentationFramework_ni+0x2fa8d2
0026cda0 581a90eb PresentationFramework_ni+0x2f9dc5
0026ce68 5817475a PresentationFramework_ni+0x2f90eb
0026d074 5fbf73c3 PresentationFramework_ni+0x2c475a
0026d0f8 581aa8d2 PresentationCore_ni+0x1a73c3
0026d14c 581a9dc5 PresentationFramework_ni+0x2fa8d2
0026d1e4 581a90eb PresentationFramework_ni+0x2f9dc5
0026d2ac 5817475a PresentationFramework_ni+0x2f90eb
0026d4b8 5fbf73c3 PresentationFramework_ni+0x2c475a
0026d53c 581aac5b PresentationCore_ni+0x1a73c3
0026d574 581adc20 PresentationFramework_ni+0x2fac5b
0026d58c 5817475a PresentationFramework_ni+0x2fdc20
0026d798 5fbf73c3 PresentationFramework_ni+0x2c475a
0026d81c 5819d65f PresentationCore_ni+0x1a73c3
0026d8f4 5817475a PresentationFramework_ni+0x2ed65f
0026db00 5fbf73c3 PresentationFramework_ni+0x2c475a
0026db84 581aaa7e PresentationCore_ni+0x1a73c3
0026dbcc 5817475a PresentationFramework_ni+0x2faa7e
0026ddd8 5fbf73c3 PresentationFramework_ni+0x2c475a
0026de5c 581a8dbc PresentationCore_ni+0x1a73c3
0026df1c 5817475a PresentationFramework_ni+0x2f8dbc
0026e128 5fbf73c3 PresentationFramework_ni+0x2c475a
*** WARNING: Unable to verify checksum for C:windowsassemblyNativeImages_v4.0.30319_32Microsoft.VisualStu# ae881ae2f569623ae0b15ace2014e6fMicrosoft.VisualStudio.Platform.VSEditor.ni.dll
0026e1ac 5aaf13a7 PresentationCore_ni+0x1a73c3
0026e1e4 5aaf0bbe Microsoft_VisualStudio_Platform_VSEditor_ni+0x1413a7
0026e930 5aaef876 Microsoft_VisualStudio_Platform_VSEditor_ni+0x140bbe
0026e94c 5ab0e518 Microsoft_VisualStudio_Platform_VSEditor_ni+0x13f876
0026e994 5ab0e47c Microsoft_VisualStudio_Platform_VSEditor_ni+0x15e518
*** WARNING: Unable to verify checksum for C:windowsassemblyNativeImages_v4.0.30319_32WindowsBasef1f3a74eb37b27b7d05b8ffa941f8473WindowsBase.ni.dll
0026e9b0 6058fac2 Microsoft_VisualStudio_Platform_VSEditor_ni+0x15e47c
0026e9f0 605929b5 WindowsBase_ni+0xafac2
0026ea3c 60592918 WindowsBase_ni+0xb29b5
0026ea54 654d21db WindowsBase_ni+0xb2918
0026ea64 654f4a2a clr!CallDescrWorker+0x33
0026eae0 654f4bcc clr!CallDescrWorkerWithHandler+0x8e
0026ec1c 654f4c01 clr!MethodDesc::CallDescr+0x194
0026ec38 654f4c21 clr!MethodDesc::CallTargetWorker+0x21
0026ec50 6556f5f8 clr!MethodDescCallSite::Call+0x1c
0026ee34 6556f74f clr!ExecuteCodeWithGuaranteedCleanupHelper+0xbb
*** WARNING: Unable to verify checksum for C:windowsassemblyNativeImages_v4.0.30319_32mscorlib4ff1f12a08d455f195ba996fe77497c6mscorlib.ni.dll
0026eee0 61de4cba clr!ReflectionInvocation::ExecuteCodeWithGuaranteedCleanup+0x138
0026ef18 61de7f34 mscorlib_ni+0x234cba
0026ef38 60592848 mscorlib_ni+0x237f34
0026ef78 6058e57e WindowsBase_ni+0xb2848
0026efbc 6058e70f WindowsBase_ni+0xae57e
0026effc 6058fdb6 WindowsBase_ni+0xae70f
0026f048 6058fce5 WindowsBase_ni+0xafdb6
0026f068 6058fb93 WindowsBase_ni+0xafce5
0026f080 6058fac2 WindowsBase_ni+0xafb93
0026f0c0 6058e050 WindowsBase_ni+0xafac2
0026f104 6058f5e0 WindowsBase_ni+0xae050
0026f180 76c786ef WindowsBase_ni+0xaf5e0
0026f1ac 76c78876 USER32!InternalCallWinProc+0x23
0026f224 76c789b5 USER32!UserCallWinProcCheckWow+0x14b
0026f284 76c78e9c USER32!DispatchMessageWorker+0x35e
0026f294 65c8d42b USER32!DispatchMessageW+0xf
0026f2a4 65c8d521 msenv!ProcessMessage+0x69
0026f2e0 65c930cb msenv!CMsoCMHandler::EnvironmentMsgLoop+0xd8
0026f320 65c92ffc msenv!CMsoCMHandler::FPushMessageLoop+0x156
0026f344 65c92f5d msenv!SCM::FPushMessageLoop+0xab
0026f360 65c92f2a msenv!SCM_MsoCompMgr::FPushMessageLoop+0x2a
0026f380 65c92e6c msenv!CMsoComponent::PushMsgLoop+0x28
0026f418 65badb92 msenv!VStudioMainLogged+0x553
0026f444 013f8fd0 msenv!VStudioMain+0xbc
0026f47c 013f3277 vbexpress!util_CallVsMain+0xfd
0026f768 013f46cc vbexpress!CVBExpressId::Run+0x8d9
0026f798 0140d01d vbexpress!WinMain+0x9c
0026f82c 76bd1194 vbexpress!operator new[]+0x1e1
0026f838 77aab429 kernel32!BaseThreadInitThunk+0xe
0026f878 77aab3fc ntdll!__RtlUserThreadStart+0x70
0026f890 00000000 ntdll!_RtlUserThreadStart+0x1b
Any Good??
Brad
Also this was at the beginning which shows the symbolPath setup
*** wait with pending attach
Symbol search path is: SRV* msdl.microsoft.com/…/symbols
Executable search path is:
ModLoad: 013e0000 01472000 C:Program FilesMicrosoft Visual Studio 10.0Common7IDEvbexpress.exe
ModLoad: 77a50000 77b8d000 C:windowsSYSTEM32ntdll.dll
etc……
Ryan,
I don't know if this helps but while waiting for your response I have continued to work with the IDE and have found it only crashes when I attempt to enter information into brackets. ??
Brad
@Brad
No, unfortunately we aren't getting the info in the above posts ;( Can you try this, do everything as before but instead of doing kp or any of that type the following instruction in WinDBG after VS has crashed
.dump /ma <some path you will be able to easily locate>vscrash.dmp
or call it anything you want (doesn't have to be vscrash.dmp, but having the .dmp extension is probably best to make loading it easier on my end). Once that has completed (may take awhile) post back here and I will find a way for you to get it to me (it is a large file, a few hundred megs at least).
Ryan
Hello Ryan,
I have created the dump (434MB). I have a Dropbox account, can I drop the file there and give you access to it??
Brad
@Brad
That should work, you can shoot me any details at rmolden AT microsoft DOT com.
Ryan
@Brad
I grabbed the dump file and took a look at it, it seems there is an ArgumentOutOfRangeException being thrown in WPF. No one on that team has seen this failure before. Could you send me the code file you are editing when it happens (or is it any code file?) and your font settings information for the editor?
Ryan
Hello Ryan,
It occurs only on the laptop and on any project. I created a new Windows Form Application and started a load sub. As soon as I typed InputBox( the error occured. It seems only to occur when I try to type after opening the bracket. I can cut & paste into the brackets without a problem. By font settings do you mean Debug > Options & Settings > Environment > Fonts & Colors
if so the settings are: Recent files = 10 items shown in both textboxes.
Visual Experience is ticked for Automatically adjust…
Show status bar is ticked
Close button affects… is ticked
Auto Hide … is NOT ticked
Brad
Sorry Ryan that was the Environment settings Fonts & Colors are many. I have also reset the font options to default with the same results.
@Brad
Can you try a quick test of something for me? Can you disable the font cache service and see if this continues to repro?
You can launch the service console by invoking %windir%System32services.msc (if you are on Vista or Win7 you can likely just type Services in the search bar of the Start Menu and it will find it for you).
When the dialog comes up you want to look for something called Windows Presentation Font Cache 4.0.0.0 (XP/Vista) or "Windows Font Cache Service" (Win7). When you find it double click on it and push the Stop button in the dialog that pops up as well as setting the 'Startup Type' combo to 'Disabled'. Then start VS and try to reproduce the crash.
Ryan
@Brad
Also, what OS are you using and can you share the exact text you are entering that triggers this? Is it any text at all or just specific text?
Ryan
Ryan
You Found IT!!!! The Cache is turned off and I can't reproduce the crash. I am using Win7 and the crash occured everytime I used an open bracket (brace).
However it appears the problem has been found. How important is Font cashing?
Brad
@Brad
Actually a guy on the WPF did, I am just the messenger 🙂 The font cache is a performance booster for WPF apps (all, not just VS), it would be important in apps that make heavy use of text rendering, say like an editor :).
It sounds like your font cache got corrupted, there are some known instances of this happening due to graphics drivers, see here: support.microsoft.com/…/937135
Those instructions won't work for you though as they are for the 3.0 FontCache and VS 2010 (on Win7) is using the DWrite font cache. I will check with the WPF guys about how we can delete that font cache (it will be rebuilt by the system, so deleting it is fine). It will likely involve similar steps to the KB above, with a differently named file. That should allow you to turn back on font caching and not have VS crash 🙂
In the meantime checking if you have the latest video drivers would be good. If you do and we get the font cache deleted and re-enable the service and it starts happening again we would love to know more about your video card, perhaps it too is corrupting the cache and it is one we are not yet aware of.
Ryan