Search Issue Tracker

Fixed in 2020.2.X

Duplicate in 2019.4.X, 2020.1.X

Votes

16

Found in

2019.1

2019.2

2019.3

2020.1

Issue ID

1175847

Regression

No

[Linux] Editor does not quit when pressing the X button

Linux

-

How to reproduce:
1. Create a new project
2. Enter Play mode
3. Exit Play mode
4. Press X to quit the Editor

Expected results: Editor shuts down
Actual results: Editor does not shut down, however it becomes unresponsive

Notes:
- It is not always reproducible, but it's mostly when a lot of work has been done on a beefy project (building, importing, loading)
- Up until 2020.1.0a8 this was always reproducible when the current platform was set to Android
- If this reproduces, the 'Unity' process disappears and the only way to quit the Editor is to kill the 'Main Thread' process
- When and if it crashes, similar stack traces to this are thrown:
#0 0x0055b7b70f3004 in DualThreadAllocator<DynamicHeapAllocator>::ValidateIntegrity(void const*) const
#1 0x0055b7b70e1702 in MemoryManager::Deallocate(void*, MemLabelId const&, char const*, int)
#2 0x0055b7b4e30c97 in dynamic_array<unsigned char, 0ul>::~dynamic_array()
#3 0x0055b7b7735895 in Texture2D::DestroyTexture()
#4 0x0055b7b766e838 in Cubemap::~Cubemap()

As of 12/5/2020 the bug doesn't exhibit crashing anymore

  1. Resolution Note (fix version 2020.2):

    Fixed in version 2020.2.0a8

Log in to vote on this issue

Comments (15)

  1. rkbain

    Feb 07, 2024 00:40

    Still affecting several unity editors launched from unity hub 3.7.0 on Ubuntu 22.04.
    The latest comment by MACIEJW94 works great, but searching the manual of nvtop did not show a non-interactive way to kill the hanging thread. So I got the PID from nvtop and played around with pkill flags to find a way to consistently kill the thread with BASH code:

    sudo pkill -9 -fi Editor/Unity

  2. maciejw94

    Jan 21, 2023 14:47

    works when you use ``nvtop`` not htop - tool like htop but for GPU processes.
    check the unity process -> F9 and scroll to option 9 to kill

  3. mbhagat

    Jul 11, 2021 08:31

    Started happening with unity hub upgrade 2.4.4.0
    Unity version 2019.3.10f1

  4. gabriela_jiang

    Apr 16, 2021 07:05

    Still an issue on Ubuntu 20.04 when using Unity version 2019.4.13f1.

  5. NlaakStudios

    Aug 23, 2020 19:30

    Still there in Ubuntu 20.04 LTS & Latest Unity Hub (Unity 2020.1.3f1)

    File-> exit does not work
    Right Click-> close does not work
    and HTOP KIll on the MANY threads does not work

  6. sandstedt

    Jul 06, 2020 07:07

    Same problem still happens in Unity 2019.4.2f1 LTS after building to Android (Oculus Quest) using Ubuntu 20.04 LTS. Need to restart my computer to close it.

  7. amyblank

    May 20, 2020 17:17

    I'm also having this issue, tested with 2019.2.6, 2019.3.5, 2019.3.11, 2019.3.14. It also freezes when I try to re-enter play mode. Been using "pkill -9 PID" to work around it, but it's definitely slowing down my development. I'll be anxiously awaiting any fix or better workaround for this!

  8. cgmaniac554

    May 15, 2020 17:49

    I have been using Unity 2019.3.12f1 on my Pop OS 20.04 for building Android Projects. Recently, this issue has been occurring most of the times. I make VR projects using Unity.

    Unable to use the "kill" command to kill the process.

  9. Achie1

    May 12, 2020 16:44

    I have the same problem. Using Unity 2019.3.13 on Ubuntu 20.04. But I only have this issue when I do Android build.

  10. pvqr

    May 10, 2020 14:03

    Can confirm, happening on 2019.3.11f1 everytime I build to Android. If I'm not building to Android, application works as expected and closes normally.

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.

Latest issues

See all new issues