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
Comments (1)
-
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.