I recently updated to UE 4.4.1, and cleaned out/installed most of the newer free Marketplace projects. I left the UE Launcher open overnight, and most of today, and came home to my system having rebooted.
Checking the Windows Event Log, I see the following entries:
1:35pm: Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: UnrealEngineLauncher.exe (3636) consumed 15723429888 bytes
1:40pm: UnrealEngineLauncher.exe (3636) consumed 15788539904 bytes
1:45pm: UnrealEngineLauncher.exe (3636) consumed 15856898048 bytes
This goes on for a bit until finally:
2:10pm: UnrealEngineLauncher.exe (3636) consumed 16109260800 bytes
My system has 16GB of RAM, so this caused Windows to panic and restart.
Looking at the Launcher log file, there are many entries of the following (~6GB worth), from 8:00pm yesterday up until 2:05pm today:
[2014.09.03-21.05.32:397][ 0]LogStreaming:Warning: Failed to read file ‘C:/ProgramData/Epic/UnrealEngineLauncher/Data/EMS/UnrealEngineLauncher/vault_Reflections.png’ error.
[2014.09.03-21.05.32:397][ 0]LogStreaming:Warning: Failed to read file ‘C:/ProgramData/Epic/UnrealEngineLauncher/Data/EMS/UnrealEngineLauncher/vault_Stylized.png’ error.
[2014.09.03-21.05.32:397][ 0]LogStreaming:Warning: Failed to read file ‘C:/ProgramData/Epic/UnrealEngineLauncher/Data/EMS/UnrealEngineLauncher/vault_VehicleGame.png’ error.
It appears the during the installation of the Marketplace content, the UE Launcher was unable to grab the images for three of the demo programs, which lead to the launcher continually increasing it’s memory footprint (~8MB/5 minutes, give or take).
It would help even more if you could get us verbose logs of this event happening again. To get verbose logs, you need to navigate to
C:/Program Files/Launcher/Engine/Programs/NoRedist/UnrealEngineLauncher/Config and open the file DefaultEngine.ini (in notepad, for example). At the end of the file, add the following text:
[Core.log]
LogHttp=veryverbose
LogOnline=veryverbose
Save the file, and then if possible reproduce the error. Afterwards, the log file you’re looking for should be the most recent one in C:/users/USER_NAME/appdata/local/unrealenginelauncher/saved/logs .
After you get the verbose logs, you may want to change DefaultEngine.ini back to make sure you don’t waste disk space on more verbose logs.
I tried duplicating the issue, but am unable to. From the looks of it my launcher may have been out of date/partially updated, which might have lead to the above issue, as the launcher looks quite a bit different after having re-launched it.
I will keep my eyes open for the same thing cropping up again, but it may have been a one-time occurrence
Seeing the same thing - there seems to be some leak in UnrealLauncher. System with 16GB RAM was at 100% commit charge after being left overnight, with low VM warning. Event log showed:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: UnrealEngineLauncher.exe (3240) consumed 523390976 bytes, avp.exe (2072) consumed 376832000 bytes, and chrome.exe (10180) consumed 285159424 bytes.
Closing UnrealLauncher immediately took commit charge down from 100% down to only a few %.
Could you follow the steps I left for Drakia to get a Verbose log of this event happening again tonight? That would make it much easier for us to find out what’s causing it.
Hey seasa,
Thanks for providing the log file. We’ve been able to repro the problem at our end, and have put a solution in place to fix the memory leak. This will be shipped with the next release of the launcher.
Sorry to hear you’re experiencing this. We were pretty sure we had this one fixed, so I wonder if it could be some other problem you’re experiencing? It would be great if you could supply us with verbose logs so we can look into this in more detail for you.
To get verbose logs, you need to navigate to C:/Program Files/Unreal Engine/Launcher/Engine/Programs/NoRedist/UnrealEngineLauncher/Config and open the file DefaultEngine.ini (in Notepad, for example). At the end of the file, add the following text:
Save the file, and then if possible reproduce the error. Afterwards, the log file you’re looking for should be the most recent one in C:/users/USER_NAME/appdata/local/unrealenginelauncher/saved/logs .
After you get the verbose logs, you may want to change DefaultEngine.ini back to make sure you don’t waste disk space on more verbose logs.
I left the launcher running minimized for several days with PC unattended. The only thing that I did with the launcher upon running was download and install 4.5 preview on the machine and then left it open.
Resulted in nearly 10GB of used memory when I returned.
Can you get us a verbose log of this happening (you don’t have to go all the way to 10gb memory used, though!)? The memory leak affecting seasa should be plugged, so you may have found a new one.
We haven’t heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you’re still experiencing this issue, please post you’re Verbose Logs that Jonathan asked for above…
i also noticed that this directory ( AppData\Local\UnrealEngineLauncher\Saved\Logs )
don’t flush the older logs and since last march i had accumulated like 2.5gb of logs, it would be probably better to not waste all that space for these very old logs.
Thanks for your report, RedEyes. We’ve since released a new version of the Launcher. Can you try to reproduce the memory leak again to see if the Launcher update fixed it?
Just some feedback on the launcher: The launcher just did an update to 1.8.2 (Mac OS X 10.10) and I updated the editor to 4.5.1. When I closed the launcher, it “closed” but persisted in the background, meaning, the dock icon for the app was properly showing it was closed, but was still showing in the Activity Monitor. The only reason I noticed it was due to the icon showing within tab switching display. I had to force close the launcher in the Activity Monitor and it also generated an abnormally large manifest under /Library/Application Support/Epic/UnrealEngineLauncher/Data/Manifests/.
I started/closed/restarted the launcher a few times, but it’s not repeating it, might just happen after an update?
