Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0a1
2018.2.6f1
2018.3.0a1
2019.1.0a1
Issue ID
1078568
Regression
No
Unity crashes on GC_push_all when using Publish() method on update()
How to reproduce:
1. Open attached project ""repro_1078568"
2. Open and launch scene "GazeboSimulationScene"
3. Wait for few seconds
- You receive error "Fatal error in GC (Unexpected mark stack overflow)" and unity crashes/freezes
Reproducible with: 2017.4.17f1, 2018.3.1f1, 2019.1.0a12
-
ivmai77
Aug 16, 2019 17:33
I wounder if it's reproducible with this fix - https://github.com/ivmai/bdwgc/commit/cbed8d14f447c8
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Test case is spawning thousands of threads which hits a limit in the GC. Ideally we would not crash, but it's hard to detect what number of threads causes the GC to reach it's limit.