[4.6.1] UMG eats up all RAM with the following steps!

anonymous_user_958fa14f · January 22, 2015, 5:46am

I’ve tested the following steps on 3 different computers, so I suppose this is worth a report!

Disclaimer: Do not try this at home! Dissonanceint is not responsible for any damage done to your PC!

Create a UMG Widget
Add a circular throbber
Set number of pieces to 99999999999999999999 (May vary according to RAM available)
???
Profit

I would have expected there to be some sort of limitor to the value or an “out of memory” error, but ue4 just starts eating all the RAM available.

Using Binary 4.6.1.

anonymous_user_e729f54e · January 22, 2015, 3:15pm

Hello dissonanceint,

I was unable to reproduce the exact result that you are seeing. Could you provide the dxdiag for one of the machines that you were able to reproduce this issue on?

I did however write a report ( UE-8046) on the fact that it does need a limit and has the potential to take up most or all of the users RAM. I have submitted it to the developers for further consideration. I will provide updates with any pertinent information as it becomes available.

NOTE: Here is the number I tried:

999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
999999999999999999999999999999999999999999999999999999999999999999999999999999999999999

anonymous_user_958fa14f · January 22, 2015, 6:17pm

Upon further inspection, the problem is very project specific (was running the same project on all PCs). I couldn’t reproduce the issue in a blank project. Anyways, setting an upper limit to the number of pieces seems to fix the issue so I’ll mark this as solved!

p.s. “Here is the number I used” = comment of the year.