UE4-Editor.exe remains in the background after exiting Editor after Packaging Project

After packaging a project, when the Editor is exited the process (UE4-Editor.exe) will remain running in the background for up to 10 minutes. This does not appear to occur from any other actions. During this time the process will use large amounts of memory and cpu. So far have noticed it use up to around 70% CPU Usage and over 10GB of RAM.

No logs are created during this time.

After using Resource Monitor while this happens, it appears the process is accessing only C:\pagefile.sys for the entire 10 minutes.

To reproduce this:

  1. Start/Open a project in UE 4.12 (I’m running 4.12.3)
  2. Once loaded in the editor, select File > Package Project > Windows > Windows (64-bit)
  3. Select any directory and press OK on the next popup
  4. Wait for it to finish packaging
  5. Once the packaging is complete, open Task Manager
  6. Find the process UE4-Editor.exe in the list of processes
  7. Go back to the Editor and select File > Exit
  8. In Task Manager watch the UE4-Editor.exe process and time how long it sits there in the background

Hi Xennma,

Unfortunately I have not been able to reproduce this on my end with the steps provided. Is this occurring with a specific project/template or is it any project/template?

Xennma,

Thanks for your report. We have not been able to reproduce this issue. It’s been tested on a couple of computers now. I’m wondering if it’s relating to the type of template you’re on, or the fact that you have an AMD powered computer.

Please provide additional details if you have them, thanks!

I have been trying to reproduce this with more information to provide but unfortunately I haven’t had any luck either in having the issue occur on newly made projects so far. It was originally reproducing on the ThirdPersonBP Template.

I am however still able to reproduce it on my main project every single time. Which was based off the ThirdPersonBP Template from an earlier engine version and has been upgraded to 4.12. I’ve attempted to replicate different variables of my main project, which continues to have the issue occur, on newly made projects but it’s not occurring now. Things I’ve attempted to replicate on new projects:

  1. Objects in level
  2. Project Settings
  3. World Settings
  4. Objects in project
  5. Blueprints in project

Now with all that being said, replicating just the blueprints in a new project of ThirdPersonBP Template did create the extended packaging time of ~20 minutes. The UE4Editor.exe process did not remain running for an extended period of time though. I decided to copy just the ThirdPersonBP Content folder, which contains all my Animations, Blueprints, Character, Maps, and Meshes files (almost all of which are the normal default ThirdPersonBP Template files + StarterContent) and that did manage to reproduce the reported issue.

Have you tried deleting your Saved and Intermediate folders from your project before? If not, could you try that and see if it makes a difference? Also, have you ever duplicated your project and seen whether or not it reacts the same way?

Thanks!

After deleting both the Saved and Intermediate folders from the project and attempting to package it again resulted in the same reported issue.

I attempted to Clone the project via the Epic Games Launcher and oddly it cloned everything except for my main folder ThirdPersonBP located inside of my Content folder. I manually copied it from the original project to the newly cloned version and attempted to package it once more. The same reported issue occurred again. I haven’t experienced the Clone function leaving out files or folders before in the many times I’ve used it in the past. Perhaps this is an indication that one or more of the files within that folder is causing this issue?

It’s very possible. Is there anyway you can try copying just that one folder to a new project and try to package? If that newly created project with that folder doesn’t package properly, please upload the log as a .txt file.

It may be beneficial to upload your project and provide it to me in a private message on the forums. If you’re able to. You’ll have to upload it to or Drive first.

Let me know how that goes -

The newly created project, as before, did package successfully still.

I’ve sent you a private message on the forums with a link to the project files.

Thank you for sending me your project. I opened it and followed the steps provided previously and did not notice a hang in RAM usage. I noticed that basically instantly, the GB went down by about 7 GB.

It’s possible that it could fall back on the fact that you have an AMD set up, I have an Intel set up. I also have double the RAM.

I checked on a local machine that is running an AMD card but it also has a similar set up to mine and I did not notice any delay in closing out the program and providing the resources back to the computer.

Are you running any programs in the background that would some how latch onto the UE4 program and cause the exit to hang for a bit? Are you running any programs that would make the resources spike, such as Visual ?

Thanks!

I have attempted to start my workstation, close any startup programs, with nothing but the essential windows processes running,

  1. Start the Epic Games Launcher
  2. Directly launched the project
  3. Successfully packaged for Win64
  4. Opened Task Manager
  5. Found the process displaying in the Applications and Processes tabs
  6. Exit the Editor
  7. The process then disappeared from the Applications tab (as expected)
  8. Switched to the Processes tab and watched the process continue to run for an extended period of time still

I have also tried doing a Clean Boot to see if the issue would still occur, and it did. I then tried again with doing a normal boot and leaving my startup programs running and the issue still occurred. From all of that no programs should have been latching onto the editor process.

Xennma,

Thank you for testing this further. I too have went through the same steps as you have and have noticed it taking roughly 8 seconds at most to close. No matter if I load the editor up right away and exit out, or work in the editor and then close out the program.

What I would suggest is that if you notice the editor is hanging up on your machine when you’re trying to close it, open up the task manager and end the process entirely.

If you are able to get this to reproduce on another machine, please provide the specs of that machine as well and also provide exact time limits which it takes to close.

Thanks again!

This happens to me as well. I have to manually shut it down in the process tree. It’s just a demo project so I’m pretty whatever the editor wants to do with it (saving/closing) should be done in 60 seconds at most.