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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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'