Visual studio 2008 sp1 hangs frequently when using XAML designer - by Peter Buelens

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 366606 Comments
Status Closed Workarounds
Type Bug Repros 14
Opened 9/8/2008 2:14:27 AM
Access Restriction Public


The title says it all. Visual Studio 2008 sp1 hangs frequently when using the XAML designer (in "view XAML mode", no less).
The problem is random but usually occurs after long editing sessions. The "visual studio is performing an operation" icon appears in the lower right corner when this occurs.
The only remedy is to kill devenv.exe.
A .DMP file generated while devenv.exe was hanging has been generated, and attached to this report.
Every time Visual Studio will hang, I will generate a DMP file and attach it to this report.
Sign in to post a comment.
Posted by Mark [MSFT] on 2/9/2009 at 12:21 PM
Hi pb_pb

Detailed analysis of your dumps reveals that you do indeed appear to be seeing the same issue as currently tracked by Connect Bug 362619

I will therefore be closing this bug as a duplicate of that one.

We are in the process of testing a potential fix for this issue. I would like to invite you to participate in a trial of this fix.

The test work will involve installing a pre-release Hotfix for the WPF designer in Visual Studio on a machine with Visual Studio 2008 SP1, then performing your normal WPF development activities for 2-3 weeks and seeing if the hang you have been experiencing re-occurs. The Test Hotfix will be in the form of a full install/uninstall package, which should enable you to roll back to your previous state of Visual Studio 2008 SP1 as needed. In spite of this, as with all pre-release software, you should be aware that unexpected behavior can occur, and if you are not comfortable with this you should not sign up to help out with the test.

Qualifications to participate in the test are:
1. You have regularly seen the issue which is described in this Connect bug in the course of your WPF development
2. You will be doing regular WPF development over the next month using Visual Studio 2008 SP1
3. You are willing to take on the risk of unexpected behavior inherent with testing pre-release software

If you meet these qualifications, and are willing to participate, please let me know by emailing me at mwthomas at microsoft dot com with the email subject line set to "Volunteering to test for Connect Bug 362619". I will be selecting 20 qualified participants and then closing the invitation.

Thank you once again for your feedback and patience in working with us to fix this problem,


Mark Wilson-Thomas
Program Manager, WPF+Silverlight Designer, Visual Studio Team
Posted by emarzeeman on 2/3/2009 at 9:38 AM
I'm getting this on a regular basis, too. Have to kill and restart devenv.exe. I have some tools installed: Visual Assist X. Refactor, ANTS Profiler, DevExpress Tools. Not doing any XAML work. It often happens on command completion/Intellisense dropdown appearing. This is terrible, since it really impacts productivity. I think MS really needs to escalate this.
Posted by Uriah65 on 1/15/2009 at 11:55 AM
I am experienced the same issue. In a quiet complex project suddenly, when open a WPF UserControl in XAML designer, processor goes 100% busy and VS2008.SP1 freezes. The only way to continue is to killl VS process. When you open VS again ii immediately goes into 100% busy state, since it is trying to re-open the same XAML designer surface. The only way to get out of that loop is to delete your *. suo file. But again, there is nothing you can do with XAML control in question, - it is not editable\viewable in the designer.
The same project, when the other user loggin in with the different profile on the same PC behaves the same bad way! The same project on the other PC, however, works good. I have reinstalled VS and still the prodlem didn’t get away. I completely reinstall Windows XP, VS 2008.SP1 and everything else, and designer start working OK again!

All that is pretty scary, since I am in the middle of big and long project that uses Win forms as well as WPF, and I am scared to get stuck with the problem described in the middle of it.
Posted by Mark [MSFT] on 1/9/2009 at 9:08 AM
Thank you for clarifying this, that's helpful to know.

I don't think the problem you are seeing is exclusive to folks who have WCF in the mix either; I'd be grateful if other readers of this thread who are seeing this problem can tell me if they have WCF in the solutions that see the issue too.

Thank you also for your continued investigations into what's causing this - that is much appreciated.

We will continue to pursue this.

Posted by Peter Buelens on 1/9/2009 at 12:15 AM
The assumption that I am doing Silverlight developement is not correct.
It is not because Cassini is running that one is doing Silverlight developement. The application is a (standalone) WPF rich client application that communicates with a WCF service, which is another project in the same solution. That WCF service is hosted in a web application.
Running the WPF application in debug mode therfore starts Cassini, which is needed to run de web application hosting the service.

On a related note: Because I'm looking for a reproducible case, I have checked if the hanging could be related to the designer calling constructors/methods in which code could cause the hanging because they are called from the designer's execution context (vs. the correct application context), but it turns out NOT to be the case.

Posted by Mark [MSFT] on 1/8/2009 at 1:40 PM
Based on your symptoms, especially your commentary at 9/10/2008, it appears that you are doing Silverlight development rather than WPF (since you have the test Cassini webserver running). Please can you confirm that this assumption is correct?

Posted by Mark [MSFT] on 1/8/2009 at 1:22 PM
Dear pb_pb

Sorry for the very long delay in getting back to you with a response to this issue.

We have so far been unable to reproduce the issue you describe in our labs, but we will continue to study the dumps you have provided and work towards a solution.

Mark Wilson-Thomas
Program Manager, WPF+Silverlight Designer Team
Posted by Yogesh Jagota on 11/20/2008 at 4:06 AM
I am developing a simple WPF project and the hangs up are now much more frequent. After 2-3 complies/builds VS hangs almost always.
Posted by Peter Buelens on 10/10/2008 at 11:40 PM
Shakek2: thanks for your comments, but no cigar.
I never open nor use the "property grid display" (if by that you mean the "properties" panel).
I always use MSIL.
No plugin touches CodeDom.

Microsoft's response on this would be nice. It seems they are very forthcoming for problems they can solve, but not for those they can't.
Posted by ShaneK2 on 10/10/2008 at 1:29 AM

HEy I commented 373393, I tracked most of this down to the propertygrid. If you shut the properties display, you will notice that stop-and-go behaviour will subside. Also in that other feedback, I have a number of other suggestions, like, dont ever set x86 or x64, always use MSIL and make sure all your projects are consistant with that. For whatever reason, when building to specific platforms, the problems are amplified.

Also, any CodeDom plugin you have, make sure to ask that vendor to disable scanning of .XAML code ;)

** I think that it would be a good idea to have some way to control aspects of the intellisense/compiled headers/auto-tasked operations (like being able to stop the XAML parser from executing on every edit)/and other such meta-data building efforts

Also it would be nice to have a setting to mask the auto-generated.g.cs files better, so that they may be excluded from any code/scanners plugins etc..
Posted by Peter Buelens on 9/24/2008 at 4:27 AM
Another hang, another dump: devenv7.dmp

Thank you for your quick and to-the-point response.
Posted by Richard R.R.S on 9/23/2008 at 9:08 AM
im having the same issue, with vs 2008 sp1, before the sp1 ¬°everything was fine, now it hangs after compiling 2-5 mins, this ocurs when compiling a smart device app.sp1 >_>
Posted by Peter Buelens on 9/15/2008 at 5:08 AM
Another hang, another dump: devenv6.dmp
Posted by Peter Buelens on 9/15/2008 at 4:38 AM
Another dump (devenv5.dmp) has been attached.
What a waste.
Posted by Peter Buelens on 9/15/2008 at 12:22 AM
Another dumpfile (devenv4.dmp) has been attached.

Reminder: all these dumps were made by starting another instance of VS2008SP1, attaching to devenv.exe (managed and unmanaged code), breaking in the debugger and saving the minidump.
Posted by Peter Buelens on 9/12/2008 at 6:20 AM
Another dump file (devenv3.dmp) is attached, should you care to examine it.
Hangs during C# compilation
Posted by Peter Buelens on 9/10/2008 at 11:56 PM
Though it may be too soon to draw any conclusions, I made the following observation: the problem is much less frequent if all of the following are true:
- the "Shadow caches" at "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files" and "C:\Documents and Settings\[USER_NAME]\Local Settings\Application Data\assembly\dl3" are empty. After long edit/compile/run sessions, this becomes filled with subdirectories and files and as far as I could determine these are NEVER cleaned up.
- no instances of "WebDev.WebServer.exe" are running. Terminating your program doesn't terminate Cassini: perhaps part of the problem is caused by these processes not being cleaned up.
- no instances of [YOUR_PROGRAM].vsbhost.exe are running. It's the same observation as above: terminating your program doesn't remove the *.vshost.exe version from task manager.

Microsoft's silence is deafening. Please see for a related bug report.

Please don't tell me to "contact support directly". Tried it, wasted time, never doing it again.
Posted by Peter Buelens on 9/10/2008 at 5:29 AM
Another dump file (devenv2.dmp) has been attached.
It seems that the "hangs" also occur during compilation.
All the problems have one thing in common: they are all solutions with WPF projects.

Please tell me whatever you need to solve this problem. I don'thave much money, but I'm willing to do whatever it takes to solve this. Productive work on nontrivial WPF projects with Visual Studio 2008 SP1 is not possible. Other connect submissions (especially like may relate to the same problem.
Posted by Microsoft on 9/10/2008 at 3:17 AM
Thanks for your feedback. We are escalating this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team