Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2019.4
2020.3
2020.3.17f1
2021.1
2021.2
2022.1
Issue ID
1363998
Regression
No
Quitting the player that has a lot of alive objects with finalizers results in a crash
How to Reproduce:
1. Download the attached script;
2. Create an empty Unity project;
3. Attach said script to any GameObject;
4. Build a 64-bit Windows Standalone player;
5. Run the player;
6. Attach a native debugger;
7. Wait for the player to allocate 20 GB of memory.
Expected result: After freezing application quits
Actual result: After freezing debugger throws an "Access violation executing location" error.
Reproducible with: 2019.4.31f1, 2020.3.20f1, 2021.1.25f1, 2021.2.0b16, 2022.1.0a12
Note: Bug doesn't reproduce every time
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0b1