Solution to Visual Studio crash while working in XAML


logo1

If you are working in Visual Studio to design XAML pages for your Silverlight, WPF, Windows Phone or Windows 8 Store application, you might have noticed that, sometime the Visual Studio IDE freezes for a long time and sometime it crashes.

 

I faced this issue many time and later found some way to recover from that freeze to continue working. In this post, going to share you the trick. I hope this will help you.

 

Application freezing is not a new thing. It happens when any application is eating a lot of memory or the processor is too busy to doing some operations. The same happens with Visual Studio too while working in XAML editor. Few years ago, I shared a blog post “How to get rid of the XAML Design view inside Visual Studio IDE?” by which you can close the XAML design view but that will not work all the times as we may need to see the UI while changing the layout. So, what to do? Let’s check out an alternative approach that I discovered recently.

 

When you load the XAML design view in Visual Studio, it creates a new process named “XDesProc.exe” which is nothing but the Microsoft Visual Studio XAML UI Designer. In case the CPU eats a lot of memory to process it or using a huge CPU power for a long time for XDesProc, the Visual Studio freezes.

 

XDesProc

 

If you want to bring back the Visual Studio IDE to  normal mode and prevent it from immediate crash, you have to kill that “XDesProc” process. To kill the process, open task manager and navigate to the “Processes” tab. Search for the process named “XDesProc.exe” and kill it by selecting and clicking “End Process”. This will bring back the IDE to it’s normal state with immediate effect.


If you have come this far, it means that you liked what you are reading. Why not reach little more and connect with me directly on Twitter , Facebook , Google+ and LinkedIn . I would love to hear your thoughts and opinions on my articles directly. Also, don't forget to share your views and/or feedback in the comment section below.

6 comments

  1. hey Kunal,
    I just wanted to know that, does visual studio starts the XDeseProc process every time I switch to xaml or at certain situation , because I can't find the XDeseProc process in task manager

    ReplyDelete
  2. Hello,

    I think, It's really awesome. Thanks for this post.

    ReplyDelete
  3. Hello,

    I had the same problem. Both Visual Studio and Blend xaml designer were very slow. Dragging objects was a nightmare!
    I said "was" because, today i replaced my windows 8.1 x64 for windows 8.1 x86, and after that both the designer were very fast. No delay when dragging objects.

    ReplyDelete
  4. Hi Kunal,
    i am getting this everytime when i type a single letter in xaml, it shows an unhandled .net exception occurred in XdesProc. What should be done in that case?

    ReplyDelete
    Replies
    1. Try reinstalling the Visual Studio. BTW, which version of VS are you using?

      Delete
  5. Try to disable/reinstall Resharper and all other plugins for VS if you have them. This worked for me.

    ReplyDelete


 
© 2008-2016 Kunal-Chowdhury.com - Microsoft Technology Blog for developers and consumers | Designed by Kunal Chowdhury
Back to top