I guessed as much T_T
This keeps happening on UE 4.15.1
I close the editor using 600mb and stays on background growing untill it reaches 3.5gb of memory usage… computer starts to run slow… and after a few minutes the process dies and everything goes back to normal.
Pretty annoying to be honest!
Specs: I7 4770k - 8gb 1866mhz - 3 HDD with 1TB each
Hi delfrasco,
This type of thing can happen for a number of reasons. If you’d like us to investigate your case, please post a new thread in Bug Reports.
-.
This happened to me today with 4.20.3.
6GB pre-close, 8.5GB post-close. Waited 20 minutes then killed the process manually. Posting this here to underline that this problem was known before - same as the initial poster from this thread, i worked on some map design. In my case i updated a material on a rather big portion of my map, so this could be an issue with shader compiler cleanups or something in that general direction.
Yes i get the same using 4.20.3, i guess they will never fix this problem
Yes same issue here. It’s happened in the past from time to time, but since 4.20 (perhaps 4.19, not sure) it occurs all the time. The UE4Editor.exe process isn’t killed by closing the editor.
Aside from the occasional RAM leaking, having 2 editor processes open prevents from being able to save any blueprint. Therefore, I have to systematically kill UE4 editor process with the task manager whenever I restart it.
Have this problem for a while now (4.20.3 and before). Are you developing for Android? I read here about adb causing it: UE4.exe and adb.exe still work in system background after close program - Getting Started & Setup - Epic Developer Community Forums But this is 4 years old…
I have the same Problem with 4.22 and all other Versions before. The only Way is kill the Prozess with Taskmanager!
strange is also that the engine works about 15 minutes with low Ram load and then makes the RAM close. Even if I do nothing in the engine! It’s terrible to restart the engine every 30 minutes just so the Ram can be used again! There seems to be a problem with the engine and the Ram allocation. The engine is stuck in the Ram even if nothing is done and uses more and more Ram until it is busy!
4.26.2 same issue… After closing editor, it starts using very high percent ram and disk. even more than while i use editor.