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
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
-
mbhagat
Jul 11, 2021 08:31
Started happening with unity hub upgrade 2.4.4.0
Unity version 2019.3.10f1 -
gabriela_jiang
Apr 16, 2021 07:05
Still an issue on Ubuntu 20.04 when using Unity version 2019.4.13f1.
-
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 -
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.
-
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!
-
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.
-
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.
-
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.
-
rhodnius
Mar 24, 2020 00:11
Same here using Unity 2019.2.2f1 and 2019.2.21f1, some times it closes, and some others (when i work more time, do android builds, etc) it just wont close it, need to force close it directly.
-
se5a
Mar 09, 2020 03:52
wondered if it was a regression of this problem: https://forum.unity.com/threads/unity-wont-close.223446/
examining system monitor on Mint adb does apear to be running, but closing that does not seem to fix the problem with unity editor itself. after forcing unity editor to close using xkill, and closing unity hub, I've still got a lot of unity processes running.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ShaderUtil.GetShaderData(shader).SubshaderCount does not count unsupported subshader
- GameObject.GetComponents returns the wrong number of components
- GUI button looks different from Editor in a Build
- Live Profiler Timeline keeps losing frame data while scrolling inside Profiler window
- Input.mouseScrollDelta.y is not correctly mapped to mouse wheel when running an iOS app on Apple Silicon Mac
Resolution Note (fix version 2020.2):
Fixed in version 2020.2.0a8