Bug Application.Shutdown.CleanupMono never finishes.

Happens randomly with no prerequisites even in TOTALLY empty projects.

​

 

Same.

 

Still happens on unity 2021.2

 

Yes, still happening all the time for me.

The only way to close Unity in 2021 is to kill the process with task manager.

Every Single Day.

Wow.

 

Yup same here, seems bad.

 

Very frustrating issue...

 

There seem to be a lot of issues such as this in the Unity forum with no "apparent" developer attention.

Have any of you submitted a bug report? What's its issue ID? It helps far more to share your issue tracker ID here rather than just pointing out your frustration.

Multiple people complaining quite often proves to be time-wasting noise, but those same people voting on an issue with code attached to help reproduce a bug is far more likely to get favorable results.

Also, try not to assume there are no prerequisites, as something causes the issue; code doesn't lie.

Check the help menu in the editor to submit a bug report; it's easy. Duplicate issues are even okay, as the dev team is capable of referencing them together.

If your codebase is private, try to reproduce the issue in a new project (or a stripped-down copy) to share with the devs in your report.

If you have no idea what causes the issue, don't sweat it; just do your best to describe the situation and result then submit that bug report so others can vote on it.

 

Reported at (Case 1388272), it even happens with the brand new 2021.2.6f1

 

I usually do take the time to report issues when I am not rammed with project work but when its something easy to spot like the editor borking after a build or something that happens every time the editor is used, I often find out someone else already reported it days ago.

 

Unnecessary reply redacted

 

Let's try not to get too feisty here peeps, we're all trying to help improve the engine and to help each other succeed, thanks @AliceWasNeverHere for reminding me to report a bug of it. Let's hope it gets fixed soon!

 

I heard back from support:

Thanks for getting in touch, we actually know about this issue but unfortunately, we cannot provide an Issue Tracker link, as this bug is only tracked internally.

Workaround:
- Open Windows Task Manager.
- Find the Unity Editor process
- Expand it to show child processes
- Click the 'Node.js Server-side JavaScript' (choose the one that's for the build\WebGLSupport\BuildTools\Emscripten-win-x64\node\node.exe (you can right-click and select Open File Location to see which one this is).
- Right-click and choose 'End task'
This then closes the Unity Editor.

 

That's really helpful. Thank you.

 

This doesn't work for me.

 

Try a newer engine version I believe it was fixed

 

Late to the party, but I'm also getting the same error related to the GitHub for Unity plugin. Killing the Git-related tasks seems to do the job.

tl;dr uninstalling the GitHub for Unity fixed.

 

This issue happens every time while building android for me in Editor and in batchmode.

I wrote about the problem here
https://issuetracker.unity3d.com/is...the-player-when-exiting-after-batchmode-build
https://answers.unity.com/questions/1876721/202126-unity-dont-quit-in-batchmode-after-android.html
https://answers.unity.com/questions/947123/why-does-unity-keep-hanging-when-run-through-the-c.html

and here in 2021.2 post
https://forum.unity.com/threads/unity-2021-2-is-now-available.1187908/page-4#post-7750335

Since 2021.2.0 version till today 2021.2.11 the problem with freezing on "clean up mono" exists

 

Yes this did the trick for me. Unfortunate since I used that a lot. Shame Unity just up and abandoned it.

 

Unity3d 2021.2.12, the problem still exits

 

Still seeing this issue in 2021.3 LTS. It's been present since I updated this project to 21.2. Doesn't happen in every project though.

It's not WebGL, and I don't use the Github plugin.

For now I've set my Task Manager to default to the "Details" tab, and sort by memory which puts Unity on top so I can kill the process easily.

 

Or you can Win+R and

Code (csharp):

1. taskkill /f /im Unity.exe

After used once, it will stay in the win+r history so you won't need to type or paste it every time

PS Back in the Unity 5 time, when it was freezing every hour, I had this command bound to Pause/Break via AutoHotkey

 

thanks for the help!

 

Google brought me here, still happening with Unity 2021.3.3f1 LTS edition. :/

 

Google brought me here, still happening with Unity 2021.3.8f1 LTS edition. :/
(didn't happen on same project with 2021.3.4f1 guess I'll downgrade)

 

Dammit....
I just left the PC on all night

 

lmao. f

Problem still there with 2021.3.8f1 W11

 

The problem is still here in 2021.3.12f1, Windows 11.

 

The problem is still here in 2022.1.20f1c1, Windows 10.

 

Issue persists on 2022.2.6f1 on Windows10(64bit)

 

Still in 2022.2.7f1 on Windows 10 (64bit).
Appeared for the first time after installing the Entities.Graphics package.

 

Incase this is relevant info, i also have the full DOTS stack installed including Entities.Graphics

 

Additional Info while upgrading to 2022.2.8f1 today: I upgraded 9 Projects, 7 without ECS and 2 with ECS - no freeze on the Projects without ECS, on both Projects with the ECS packages the freezing occurs.
After deinstalling the entities.graphics package (and entities package via dependencies), the issue is gone.

 

Yup, this is a part of my life now since ~2022.2
(ECS project).

I can't even hook this with my debugger to see where this is happening, seems entirely internal. This close to whipping out IDApro or something...

 

Same 2022.2.6f1 (DOTS packages installed)

 

Same here, 2022.2.9 (with DOTS packages installed). It seems like I started having this issue when I created a new shader graph, but I am not sure

 

Still the same on 2022.2.11f1.

 

Same problem on 2022.2.14, every time I close Unity

 

same in unity 2022.2.17f1

 

I fixed the issue (or worked around it) by closing a bunch of Unity Ui elements. One of them was causing the issue, not sure which one. But with a slimmed down interface I haven't seen it in a while. Also might have been Unity VCS, which I disabled around the same time as closing a bunch of UI elements (Project Settings > Version Control > Unity Version Control Settings)

 

Changed to unity 2022.2.18, now every time I close I get this. I have to close with KILL PROCESS in win10

 

Same here. Not gonna disclose my Unity version because i am an annoying anarchist. Killing Unity in the taskmanager every day is my live now...

 

And now we are having 2022 LTS, and still have to close the Editor with the Task Manager.

 

But of course, LTS stands for Lose Time Shutting down.

Sorry, couldn't resist, hahahahahaha

 

LTS naming is just a joke, same S*** like the others...

 

For reference I solved it by just closing visual studio.

 

Unfortunately, this does not work for me. Error occurs always when I was in PlayMode, even if I never opened VisualStudio.

 

Yup, happens with LTS 2022.3.1f1... Go into Play Mode, try to close afterwards then it's a RIP

 

I finally got around this by making sure there is no Shader Graph or UI Builder window/tab open. Try just making sure all shader graphs are closed before exiting Unity.

 

I don´t use ShaderGraph, and there is no UI Builder Window open. For testing purposes, I open the project, hit start, exit playmode, then close the project -> RIP.

 

Still happens in 2022.3.2



Why is this game engine so buggy?