Visual studio crashes on breakpoint

Ever since I installed 4.7 when i debug via DebugGame Editor option, and i hit a break point, visual studio(2013 community) crashes and resets.

I noticed that I have the engine folder now in VS and I didn’t for 4,6 not sure how much that changes things. I also made sure it was a single startup project.

Anyone have any ideas?

Hi! Could you post the callstack that you get when Visual Studio breaks into the debugger please?
As of 4.7, we ship full engine C++ source code for builds installed through the launcher, which will be why you’re seeing an Engine folder where before you weren’t.

It’s not crashing today for some reason(of course!) I*'ll be sure to take pics ect if it happens again, thanks for your time.

never mind it crashed.

ActivityLog is uploaded as well
[link text][2]

oh wow, that does look very unusual. I notice in your activity log it’s reporting “Not enough storage is available to process this command” - is there a chance any of your hard drives are full up, or you’ve run out of memory somehow?

I guess you could try removing Visual Studio’s appdata folder and restarting - it’s plausible that some visual studio extension or package has corrupted something. This stack overflow thread explains something similar.

yeah, I saw that too but I have 45 gigs left on my HDD and only using 3 out of 8 gigs of ram. Task manager is showing low percentage usage in everything. I’ll check it out thanks!

I actually watched task manager and the memory for VS was almost 3k ! That’s crazy T_T And disk 100%

Is VS supposed to take up that much??

It wouldn’t be uncommon for something like VS to occasionally chomp on your RAM like that, and it doesn’t appear to be the culprit of your disk usage (which is only at 100KB/s for VS)

I’d try disabling any Visual Studio extensions/add-ons you have installed to see if any of those are at fault.

Does this happen every time you hit a break point? Do any other smaller projects work ok in visual studio (try creating a new empty console application or something)?

Actually I realize it’s any time I debug. The break point probably just takes up more memory so that’s why it crashed. non debugging takes only 149 mb + 529 mb for the C++ package.

I don’t know what’s up with the disk usage. nothing ever shows more than 3mb. Very concerning…

i’ll try some stuff out , thanks for the help!

Oh, wait - I just noticed you’re running the 32 bit version of Visual Studio. A 32 bit process will be limited to ~3.5GB of memory due to the limited address space.

If possible you should try with a 64 bit version!

EDIT: Ok, I just realised there is no 64 bit visual studio (my bad). I guess that somehow having all the engine source, or PDBs loaded during debugging is causing it to consume too much memory, but this is certainly unusual…

You could try unloading some of the projects in the solution and see if that helps?

This is the same project under 4.6 .

This is a new project under 4.7.1 All is well …maybe something is wrong with my project or it didn’t upgrade right. I’m going to upgrade my project again and see what happens

I build my project from 4.6 to 4.7.1 and get these errors:

Is there anything that can be done or am I screwed and I have to make a new project? :frowning:

I moved this problem to Major memory problem after upgrading - Pipeline & Plugins - Epic Developer Community Forums because break points ended up having nothing to do with it . I don’t know how to close this unless I can only resolve it.

This is fixed by regenerating the visual studio files