Search Issue Tracker

Duplicate

Votes

24

Found in

6000.0.27f1

6000.1.0a4

6000.2.0a1

Issue ID

UUM-87775

Regression

Yes

Player remains in Windows Background processes when the application is closed

-

How to reproduce:
1. Create a URP template project
2. Build the project with the name “MyProject”
3. Run the built project
4. Right click on the built project in the Windows Taskbar and click “Close window”
5. Open the Windows Task Manager
6. In the “Processes” tab search for “MyProject”
7. Observe the “Background processes” section

Expected result: No built project .exe will be found in the Background processes section
Actual result: The built project .exe is found after closing the .exe application

Reproducible with: 6000.0.0b14, 6000.0.27f1, 6000.1.0a4
Not reproducible with: 2021.3.46f1, 2022.3.53f1, 6000.0.0b13

Reproduced on: Windows 11
Not reproduced on: macOS

Note:
-Comments of previous testing mention this is not exclusive to URP as was first reported
-The processes stack multiple times if you keep opening and closing the application

  1. Resolution Note:

    This is the same bug as UUM-91181 and is being fixed there. The fix has landed in 6000.2.0a2 and backports to other active branches are on their way.
    Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-91181

Comments (4)

  1. SubbuGames

    Jan 10, 2025 08:26

    I stumbled upon this today, am on 6000.0.31f1. my case was a windowed application and if closed with alt+f4 or the close button from titlebar it would stay in the background. using application.quit works as usual and using the old input system also fixes this issue like NIFFLAS mentioned.

  2. Nicolas-Vidal-Iscool

    Jan 03, 2025 13:40

    Here is an ugly workaround @Nifflas :

    private bool _wantsToQuit;

    private void Start()
    {
    Application.wantsToQuit += () =>
    {
    if (_wantsToQuit) return true;
    _wantsToQuit = true;
    return false;
    };
    }

    private void Update()
    {
    // Workaround for Unity 6 bug :
    if (_wantsToQuit)
    {
    Application.Quit();
    return;
    }
    }

  3. Nifflas

    Dec 29, 2024 00:07

    The bug only appears to occur when the new input system is in use. If only the Old input system is in the project, it doesn't.

    I'd say this most likely has something to do with interrupting application exit via Application.wantsToQuit or Application.quitting

  4. Nifflas

    Dec 27, 2024 20:16

    I'm literally going to need to wait with releasing my game, which is just around the corner, unless this is fixed or I can find a workaround. This needs a fix asap.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.