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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment