This should not happen. I suspect this has something to do with the project rather than being a general issue. Try to strip down a copy of the project to the bare minimum that exhibits this behavior.
I would start with leaving only an empty scene in the build scene list. If this shuts down properly you know it‘s a project specific issue. Otherwise it may be a bug, a project setting (or several), an installed package or asset that still makes it into the build somehow, or less likely a system issue (eg drivers).
Hello. I’m experiencing exactly the same issue. I’m using Unity 6, and it didn’t occur in previous versions. I don’t believe it’s a problem specific to individual projects.
I encountered the same issue. I’m using Unity version 6000.0.32f1. I have two different game projects: one is singleplayer, and the other is a multiplayer game using custom TCP/UDP communication. I tested both projects with an empty scene and a normal scene, but even after closing the game, the process continues running in the background. I also tried switching between IL2CPP and Mono for builds, but none of them solved the issue.
I’m also experiencing the same issue in Unity 6000.0.32f1 where my game leaves multiple background processes running after closing. Initially, I thought it was related to the NetworkManager (Netcode) or Steam API, but after testing, I confirmed it’s not caused by them.
What’s strange is that these background processes keep stacking up. I noticed this when my computer started slowing down, and when I checked the Task Manager, there were around 20 background processes for my game, each using about 150 MB of RAM.
Additionally, I noticed a difference based on the scene loading status:
If I close the game after the scene loads, each background process uses ~150 MB of RAM.
If I close the game before the scene loads, each process only uses ~60 MB of RAM.
I just noticed that as well, Unity 6. Just upgrade to the latest version (33f1) and it happens even with a brand new project. Mine was the HDRP base template. Nothing added, just build this, run the game, close, and the process will stick in the windows process list, and never kill itself.
I’ve been waiting for Unity support, but it didn’t work, so I found this solution which works for me. Put the script below in a GameObject that exists in every scene:
using UnityEngine;
public class ApplicationQuitHandler : MonoBehaviour
{
void OnApplicationQuit()
{
if (!Application.isEditor)
{
System.Diagnostics.Process.GetCurrentProcess().Kill();
}
}
}
System.Diagnostics.Process.GetCurrentProcess().Kill(); can’t be used with IL2CPP. But looks like it can be replaced with Environment.FailFast(string.Empty);.
@vlklubkov
Thanks for the tip for IL2CPP builds! Just a note for others: Environment.FailFast() requires user input after the process terminates. Windows 10 reacts as if the app is frozen. Depending on the use case, this may not be acceptable.
@AM_FX That’s interesting, thanks for sharing! I only tested on Windows 11, and it doesn’t seem to need any user input, the app simply closes. The only side effect I experienced for FailFast() is that it creates crash report files for Development builds, a large one in %LOCALAPPDATA%\CrashDumps and a small one in %PROGRAMDATA%\Microsoft\Windows\WER\ReportQueue.
