Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.3
2021.1
2021.2
2021.2.0a19
Issue ID
1338786
Regression
No
Crash Handler opens twice when Unity crashes with out of memory
Reproduction steps:
1. Create a new empty Project
2. Try to import the package attached to case 1331683 while only about 20-50gb is left free in the Hard drive
3. Wait around 40min for the Hard drive to get full and Unity to crash
Expected result: The Crash Handler opens once
Actual result: The Crash Handler opens twice
Reproducible with: 2019.4.27f1, 2020.3.11f, 2021.1.9f1, 2021.2.0a19
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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (2021.2.X):
The handler opening twice in this instance is not expected, but as long as it is running it's behavior that doesn't meet our current bar to fix.