Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
0
Found in
2020.2.0a15
2020.2.0b11
2021.1
Issue ID
1290649
Regression
No
Crash in RenderingCommandBuffer::AddSwitchIntoFastMemory after calling SwitchIntoFastMemory method when CommandBuffer is null
Steps to reproduce:
1. Open attached "fastmemorycrash.zip" project in Unity
2. Open "SampleScene" scene
3. Enter Play mode
Expected result: SwitchIntoFastMemory doesn't cause a crash and/or throws an error instead
Actual result: SwitchIntoFastMemory crashes the Unity editor
Reproduced on: 2020.2.0a15, 2020.2.0b11, 2021.1.0a5
Older versions not tested as feature was introduced in 2020.2.0a15
Notes:
-Crash affects player builds as well
-Calling SwitchOutOfFastMemory method also causes a crash if CommandBuffer is null
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor layout does not save custom Editor windows when they are declared using file-scoped namespaces
- Crash on VFXManager::CollectShadowCullResults when opening a specific scene
- Component Glyphs value is truncated and Ligature Table glyph fields become inaccessible when increasing the Component Glyphs count
- There is no “Overwrite Preset?” popup when saving a Customizable Toolbar preset with a name that already exists
- Customizable Toolbar preset does not switch to the Unity Default Preset when Reverting All Saved Presets or deleting the active Preset
Add comment