Search Issue Tracker
Duplicate
Votes
0
Found in
2019.4.29f1
Issue ID
1345337
Regression
No
Unity Editor process remains running after closing Editor
When creating new project or opening a project without Library folder, then after closing Editor 2 processes remains running.
Those processes close themselves after 15-20 min.
How we can reproduce it
1 Create new 3D project
2 Close Editor
3 Check TaskManager
Actual results: you will see "Unity Editor" group with 2 processes in it - VBCSCompiler.exe and Console Window Host
Expected results: all those processes should be closed
Tested only on Windows
Reproduces on: 2018.4.31f1, 2019.4.17f1, 2019.4.25f1 - 29f1 (didn't check earlier versions), 2020.1.5f1, 2020.1.10f1, 2020.1.17f1 .
Not reproduces: 2020.2.0a21 - 2020.3.8f1(didn't try earlier than 2020.2.0a21) , 2021.1.6f1, 2021.2.0b1
Looks like it got fixed somewhere 2020.2.0a1 - 2020.2.0a21
-
joker123gaming
Jun 24, 2021 09:49
Joker123 is an Online Slot Gambling Site and Casino Agent with various online gambling games supported by official providers such as Hanabero, Pragmatic, etc. There are so many games you can play. For a list of games, see https://172.104.40.108/
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
- SerializedPropertyChangeEvent is invoked when initially binding PropertyFields in custom Editor
- UI Panel is not visible when HDR and STP filter are enabled
- Crash on GfxDeviceD3D11Base::DrawBuffersIndirect when opening a specific project
- OnTriggerExit2D is called in Play mode when undoing component adding
- Builds fail with "Execution failed for task ':launcher:checkReleaseDuplicateClasses'" error when the newer version of the In-App Purchasing package is installed on a specific project
Resolution Note:
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this issue.