4.9 Blueprint Freezing - Memory?

Hello,

I’ve recently been running into some stability issues running 4.9 with multiple blueprint windows. My workstation (running windows 7 64bit) has been freezing, which requires a hard reboot.

A colleague recommended turning on Page filing. Although I have 24 GB of system memory, enabling the virtual memory for windows did quell my stability issues.

System specs: 2 E5520 Xenon processors, 24 GB of DDR2 RAM, GTX 980, and multiple HDD in RAID (not sure of the array type)

Thanks!
-V

Hey Stimpanzee,

Were you noticing that the RAM was filling up before the freezing occurred?

If your memory gets out of control again, let it grow as high as you feel comfortable with. Then bring up the console with ~ and enter memreport -full. Rename the extentions on the .memreport file to .txt in the [ProjectName]/saved/Profiling/MemReports and then attach it here.

-.

PS - Could you send your dxdiag for good measure?

Experienced the same problem. It only happens when I have some particular blueprints opened in the Blueprint Editor. Memory usage will start to grow by over 3GBs in under a minute. Closing the Blueprint causes RAM usage to go down again.

However, since this is a migrated project there were a truckload of tabs opened in the blueprint editor (I think enarly every function was open in a tab). I closed them all and opened only one and the RAM usage has been stable for now. I don’t know if it was the sheer number of open tabs or if it was a specific tab that was causing the leak. I’ll keep an eye on the RAM usage as I go through the BP’s function graphs.

Hi everybody,

@Stimpanzee I am marking this as answered due to inactivity. Please respond to re-open.

@Manoelneto If you are able to track down a BP that consistently causes the memory to spike, would you mind uploading the project to dropbox or drive and PMing me the link?

-.

I’ll keep an eye for it, but I haven’t seen it happen since.

Thank you :slight_smile:

I believe I found a way to reproduce it. It seems to happen when you have a minimum amount of function tabs open in the Blueprint Editor. Here’s a minimal repro case on an empty project:

  • Create a new blueprint class
  • Open the class in the blueprint editor
  • Just keep adding new functions to that class. Keep watch of the editor RAM usage.

At some point (exactly 14 function tabs for me), the RAM usage will start to go up quickly and constantly even if you do not interact with the editor any further. Closing one or two tabs will halt the memory leakage and closing the blueprint editor will purge all leaked memory.

Hey manoelneto,

Thanks for providing that repro! I was able to get it to occur in house and it appears we’re already looking into it with UE-21203.

It took me about 20 function tabs to repro, but it appears that it is an issue directly related to the size of the tabs. I could make only 5 functions, but squish the blueprint window size until they were very small. We’re actively working on a solution, but for now, at least you know what the exact repro is and can hopefully try to avoid it.

-.