Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.2.X, 2022.1.X
Votes
7
Found in
2021.2.0a18
2021.2.0f1
2022.1
Issue ID
1391935
Regression
Yes
Crash on GC_push_all when updating custom mesh generation
Reproduction steps:
1. Open the user's attached project
2. Open "Assets/CurveDesigner/Scenes/EndlessRunnerExampleScene" Scene
3. Select GameObject "RootCurve" from the Hierarchy
4. In the "Curve3D" Script component change values of "Vertex Density" and "Ring Point Count"
Expected result: Editor doesn't crash after changing parameters
Actual result: After some time Editor throws a "Fatal error in GC: Unexpected mark stack overflow" error and crashes
Reproducible with: 2021.2.0a18, 2021.2.6f1, 2022.1.0b1
Not reproducible with: 2019.4.33f1, 2020.3.24f1, 2021.1.28f1, 2021.2.0a17
First lines of stacktrace:
x00007FF96240C496 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\external\bdwgc\mark.c:1379] GC_push_all
0x00007FF96219709B (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\boehm-gc.c:787] mono_push_other_roots
0x00007FF962409B3A (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\external\bdwgc\mark.c:457] GC_mark_some_inner
0x00007FF9624099EB (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\external\bdwgc\mark.c:522] GC_mark_some
0x00007FF962412CAD (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\external\bdwgc\alloc.c:832] GC_stopped_mark
0x00007FF9623FDAEC (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\external\bdwgc\alloc.c:705] GC_collect_a_little_inner
0x00007FF9623FBE69 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\external\bdwgc\alloc.c:1563] GC_allocobj
Note:
- it may take a few minutes to reproduce the crash
Comments (3)
-
rt_jscott
Feb 11, 2022 22:25
Yes this is really a problem. I would love any information how how to avoid this problem!
-
xAdamQ
Jan 22, 2022 23:48
This issue is a nightmare on all platforms, I hope a fix!
-
dduttonnc
Jan 06, 2022 03:53
I have this same issue as well.
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
- Crash on PluginManager::RefreshPlugins when closing the Editor without making any changes with JetBrains Rider selected as the External Code Editor and Google Mobile Ads third-party plugin imported
- GetMainLight() returns incorrect distanceAttenuation value for a Custom Shader when URP Forward+ Rendering Path is used
- Standalone Profiler crash on GuidReservations::Reserve when it is opened on a specific project
- m_RenderPipelineGlobalSettingsMap or m_SRPDefaultSettings is pointing to UnityEngine.Rendering.HighDefinition.HDRenderPipeline when High Definition RP package is removed
- Rendering Debugger fields have no padding at the bottom of the fields list
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a5
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0b14
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.17f1