Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.3.1f1
Issue ID
756193
Regression
No
Assigning value type to multiple parameters in same line will crash Unity
Steps to reproduce:
1. Open attached project "MultiAssign.zip"
2. Open scene "repro"
3. Run scene and Unity freezes (sometimes crashes with no stack trace)
4. Reopen project and open "Test.cs" script
5. Workaround: change line A = B = new Vector3(0, 0, 0); to B = new Vector3(0, 0, 0); A = Vector3(0, 0, 0).
6. Run scene and Unity no longer crashes
Note: This doesn't happen if instead Vector3 int is used.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Add comment