Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.3
2019.3.9f1
2020.1
2020.2
Issue ID
1237566
Regression
Yes
Exceptions in looped finally blocks corrupt memory and cause crashes
How to reproduce:
1. Download the user-submitted script(BreakIl2cppFinally.cs)
2. Create a new Unity project
3. Import the downloaded script and create a new script that calls BreakIl2cppFinally.CorruptMemory()
4. Attach the newer script to a GameObject and enter Play Mode/Build and Run for Mono/Build and Run for IL2CPP
Expected result: Editor/Player does not crash
Actual result: Editor/Player crashes
Reproducible with: 2018.4.23f1, 2019.3.13f1, 2020.1.0b9, 2020.2.0a12
Not reproducible with: 2017.4.40f1(Editor does not crash, but throws some errors, Mono build does not crash, could not test IL2CPP build)
Notes:
Crashes occur in Editor, Mono and IL2CPP builds
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
The root cause of this is a stack overflow in the way mono is handling exceptions thrown like this. A bug has been filed upstream for this: https://github.com/mono/mono/issues/19846 -- will reopen this bug once it has been fixed upstream.