Visual Studio 2010 and the memory (32-bit)

by Roland Schumacher alias GENiALi 15. Juni 2010 -- 251 words -- 1 mal gelesen

This is stuff so ne. On 32-bit systems, a process gets 2 GB virtual memory. You can not see that in the Task Manager, which are only virtual. Usually this is sufficient also loose. But there are installed in the Visual Studio 2010 multiple AddIns or extensions is quickly running out.

Then it is possible that can be copied no code suddenly stating that not enough memory was available. He was too fragmented, and then the copy fails. Visual Studio 2010 is restarted the same place without any problems can be copied. Until it again... Oh well.

When it comes very bad Visual Studio 2010 displays a message with a link to a possible solution.

Visual Studio 2010 - low virtual memory

There is described well what it is about. A solution is that it allows the operating system to give more than the 2 GB a process. 3072 MB, the upper limit for a process is increased to 3 GB. Under Vista, Windows 7 and Server 2008 to adjust an entry in the Boot Manager.

bcdedit / set IncreaseUserVa 3072

Command line (cmd.exe) as an admin start and run.

After that, both are gone. Since then, I no longer found to the problem of the copy and the strong message with too little memory. :-)

But actually I wanted to write long the posting as the original help page, which I've linked, had an error in the bcedit command. On other pages, I found the correct at the time. In between the typo at IncreaseUserVa has been fixed.