Search Issue Tracker
Fixed in 2020.2
Fixed in 2020.1
Fix In Review for 2019.3
Unity secondary processes keeps running after Unity is force closed
How to reproduce:
1. Open the "Torch" project
2. Open the "Square" scene
3. Make sure Jobs > Burst > Enable compilation is checked
4. Open the BonfireComponentSystem.cs (in packages) with Rider
5. Attach the debugger to Unity
6. Add breakpoints on line 68, 70, 72 and 78
7. Enter Play Mode
8. Once the breakpoint is hit, perform "Continue" (fn + f5) for several times
9. Perform "Step-Over" (fn + f10) for a few times
10. Remove the breakpoints from line 68 and 70
11. Perform "Continue" (fn + f5)
12. If Unity didn't freeze or crash - repeat from step 6 (without leaving Play Mode)
13. When Unity freezes open Activity Manager and filter "Unity"
14. Kill main Unity process and notice how the secondary process stays (May be only secondary process if Unity crashed)
Actual result: Secondary Unity process keeps running after Unity is killed.
Reproducible with: 2020.1.0a20, 2019.3.0f3.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Unity crashes when opening the project
- "Color Picker not supported on this platform" error is thrown when UseOSColorPicker is set to true on Windows
- Lightmap Encoding Quality settings do not apply to baked lightmap textures
- GameObject is not culled and can be seen in the Frame Debugger when Camera is facing away from it
- [UIR] Lines separating packages wiggle in Packman at 150%