Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
Votes
0
Found in
2020.1.0a19
2020.3
2020.3.8f1
2021.1
2021.2
2022.1
Issue ID
1361799
Regression
No
Build crashes with Unexpected mark stack overflow Error when building with IL2CPP
How to reproduce:
1. Open user-submitted project
2. Navigate to Edit --> Project Settings --> Player --> Other Settings
3. Make sure that Scripting Backend is set to IL2CPP and Use Incremental GC is ticked
4. Navigate to Edit --> Project Settings --> Quality
5. Make sure that VSync Count is set to Don't Sync
6. Navigate to File --> Build Settings
7. Press Add Open Scenes
8. Build and Run the project
Expected result: The Build runs until it is turned off
Actual result: The Build crashes after 0-5 minutes
Reproducible with: 2020.1.0a19, 2020.3.18f1, 2021.1.20f1, 2021.2.0b9, 2022.1.0a8
Not reproducible with: 2019.4.30f1, 2020.1.0a18
Note: If the project doesn't load press Help --> Reset Packages to defaults and delete the Library folder
Comments (1)
-
zakkaiokenx10
Feb 04, 2022 21:13
This isn't fixed it's still a problem in 2021.2.8f
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
- NullReferenceException is thrown when assigning an Object to a custom DebugUI.ObjectField in Rendering Debugger
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a12
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b16
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.26f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.21f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.33f1