Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2017.4.X, 2018.4.X, 2019.3.X, 2020.1.X
Votes
0
Found in
2017.4
2019.3.0f6
2020.1
Issue ID
1221358
Regression
No
Editor crashes on ConstantBuffersD3D11Base::SetBuiltinCBConstant when creating a new Standart Surface Shader
How to reproduce:
1. Open the user's attached project "PaintingSim.zip"
2. Open Project window and right-click on an empty space
3. Select Create > Shader > Standart Surface Shader
4. If the crash did not occur repeat steps 2-3
-- Observe the crash
Reproducible with: 2017.4.37f1, 2018.4.18f1, 2019.3.2f1, 2020.1.0a24
Note:
1. the crash occurs randomly, sometimes it takes more than 10 attempts to reproduce it
2. an assertion fails right before the crash: Assertion failed on expression: 'offset >= 0 && offset + size <= m_Buffers[cbIndex].key.size && size > 0'
3. also reproducible when duplicating multiple shader files
The stack trace:
0x00007FF6FD35B410 (Unity) memcmp
0x00007FF6FAD81611 (Unity) ConstantBuffersD3D11Base::SetBuiltinCBConstant
0x00007FF6FAD775CC (Unity) GfxDeviceD3D11Base::BeforeDrawCall
0x00007FF6FAD7BA15 (Unity) GfxDeviceD3D11Base::DrawBuffers
0x00007FF6FB6629B0 (Unity) DynamicVBO::DrawChunk
<...>
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a3
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b3
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.8f1
Resolution Note (fix version 2017.4):
Fixed in: 2017.4.40f1