Search Issue Tracker
Not Reproducible
Votes
1
Found in
5.4.0f3
Issue ID
823783
Regression
Yes
Editor crashes in RenderingCommandBuffer::ExecuteCommandBuffer
Steps to reproduce:
1. Open the attached project.
2. Press play.
As a result, Unity crashes in RenderingCommandBuffer::ExecuteCommandBuffer and it's only reproducible on 5.4
Reproduced on: 5.4.0p2, 5.4.0f3, 5.4.0f2.
Didn't reproduce on: 5.3.6f1, 5.3.5f1, 5.3.4f1, 5.2.5f1
Comments (1)
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
- Tags window completely breaks and throws Exception errors when Adding a Tag to a GameObject
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
- InvalidOperationException when using Game Camera Preview in Scene window with a custom RenderGraph pass
- Changing "PreWarm" parameters on VFX Graph leads to significant performance drops and freeze due to rapid changes in "Total Time"
- Player display resolution changes to the native resolution of the monitor when Player becomes unresponsive
Guillaume-Swing
Sep 29, 2016 16:00
Seriously that is super sad that there is so much regression this days with 5.4.
I understand that there is a lot of optimisations and changes going on... but still, those are serious crashes with no obvious workaround :(
So we are stuck in previous version of Unity after having passing some time to upgrade the code, rebuild Libraries and hoped that this will fix other vsync issue (that were not fixed for us). I'm loving it'