Search Issue Tracker
Fixed in 2020.2
Fixed in 2019.3, 2020.1
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.
- Modifying scoped registries in project manifest does not update Package Manager UI window
- Models change their position in scene after reporting them in 2019.4
- Texture 'Read/Write' option does not double the memory in Profiler
- Pixel perfect setting not applied immediately
- [PLM] Changing the Environment Volume Profile settings does not trigger a new bake