Search Issue Tracker
Fixed in 2021.1
Fixed in 2020.2
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
- Shader error db grows on each build
- Android ARCore build fails with 2019.4 due to outdated Gradle
- [tvOS] Visual artifacts are present when Ambient Occlusion is enabled and Dynamic Resolution is reduced
- Texture Importer Inspector throws errors when a built-in texture inspector is overwritten in C#
- Invalid AABB error is thrown when moving a Particle with Velocity over Lifetime and Limit Velocity over Lifetime modules
Add comment