All geek questions in one place

Visual Studio 2012 XAML design process eats memory

I just started using Visual studio 2012, and the problem with it is the designer’s process, and the devenv.exe file was eating more than one memory concert. the question here is the process of the XAML designer. XDesProc.exe never clears memory and does not load many designers at once. I do not know that someone notices this because of high memory. but I have 4 Gigs RAM, it just stumbles and uses everything in general. I also have a screenshot that shows how 200 megabytes are used only by the designer.

Task manager

Edited: it gets worse when I make an assembly, and not in debug mode in release mode, it gets stuck, and after a few minutes the application appears. enter image description here

+6
source share
2 answers

Yes, these are XAML files! Here are some suggestions:

If you are not dependent on the Design view (I never use it), I would open the XAML files as txt files so that they do not need to be compiled, which should help.

 Right-Click on the .xaml file in Solution Explorer Open with.. Select Source Code (Text) Editor Click <Set as Default> button so you don't have to do it again. Click <OK> button

When VisualStudio really pissed me off with XAML slowness. I am switching to Kaxaml . It is free and super light weight.

I also leave Windows Task Manager open and periodically kill XDesProc.exe (Visual Studio Visual Studio XAML design processes) when they appear. Probably, you just need to write a powershell script or an application that kills them .. (should be quite simple, create a timer and expire and kill it)

+11
source

This is an old stream, but, nevertheless, it may be useful for some people; I found Kill WPF Designer ", with which you can kill XDesProc from visual studio.

[Edit] You can also go to Options-> XAML Designer and uncheck the Enable XAML Designer box.

0
source

Source: https://habr.com/ru/post/949242/

More articles:


All Articles