Try our conversational search powered by Generative AI!

Visual Studio 2012 runs out of memory when debugging



I´m having problems with debugging my EPiServer 7 solution in VS2012. When I press the play button the browser starts but it crashes after a couple of minutes and the startpage was never shown. I can see in the Windows Task Manager/performance that the memory is used to 100%. I have 4GB of RAM. I tested with 6Gb of RAM and the problem is the same. The system eats ap all memory and Visual Studio crashes with the following message "A fatal error has occurred and debugging needs to be terminated.  For more details, please
see the Microsoft Help and Support web site.  HRESULT=0x8007000e.  Error Code=0x0."

I think this problem started when I went from declaring all page types in the database to create page types with code. If I exclude a couple of pageTypes from the solution I can debug. It´s using a lot of memory but not all memory.

I have tried both Casini, IIS-express and IIS and the problem is the same.

Does anyone know what the problem can be?

Aug 23, 2013 10:51

You could try to memory profile your application. There are some user friendly .NET profilers like e.g. Otherwise you could take a crashdump and look into it using WinDbg.

Aug 23, 2013 11:02

Thank you I will try that one.

I think it´s very intresting why our Models/Pages with all PageTypes classes are eating all memory. If I exclude them from the project the memory consumption doesn´t rise above 47%. And if I include them in the project the memory consumption is 100% and Visual Studio crashes.

Does anyone have any idea why?

Aug 23, 2013 14:27

That is not of course the intended behaviour. My guess is that some code enters a infinite loop or similar that causes the problem.

Aug 23, 2013 14:28

How about the cpu when the problem occur, is it spinning at maximum?

Aug 23, 2013 14:31

The CPU does not spin att maximum. Aproximately 50%.

Aug 23, 2013 16:23

I am having the same situation when debuging epi7 project in vs2010 and vs2012. Based on memory profiling, it appears the contentDataActivator is scanning all page types defined in code and each page type eat about 80m memory. So if you have more than 35~40 page types defined in your project, most likely your VS IDE will run our of memory(Max 3G). Is anyone else experiencing the issue and know is there a workaround or not?

EPiServer.dll!EPiServer.DataAbstraction.RuntimeModel.ContentDataActivator.Create(System.Type contentDataType) Line 36 + 0x3d bytes

Nov 04, 2013 23:56


How many page types do you have? In our solution we have aproximately 70 page types. I still haven´t managed to solve this problem.

Nov 05, 2013 16:21

We have about 60 page/block types and haven't find a way to work around it neither. Hope we can get more insights from the episerver team. 

Nov 05, 2013 18:34

We also have this problem. Vs2012, EPiServer 7.1 and win 7 64 bit. 

Nov 05, 2013 19:54

Just a short update, the developers have investigated a client's project today with the following result:

They arent 100% sure if its caused by Visual Studio or EPiServer. When starting the debug in Visual Studio for an EPi project several modules are initialized and this seems to cause some kind of memory leakage in VS. 

Workaround for now is to avoid hitting F5 in VS to start up the debugging, instead using the function Attach to process. While testing on the client's server this didnt crash VS so hopefully it helps everyone.

Edited, Jan 24, 2014 17:51

One of our projects shows the same behaviour when using IIS Express and "Play button" in VS 2012. But when switching to local IIS and using "Attach to process" debugging works as good as it should.

Jan 24, 2014 22:10

check first the program's basic system requirement

Mar 16, 2015 10:38
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.