Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
5
Found in
2022.1.24f1
2022.2.1f1
2023.1.0a23
2023.2.0a1
Issue ID
UUM-21092
Regression
No
[M1][Silicon]Player window freezes when resizing rapidly
Reproduction steps:
1. Open the attached project “ReproFreeze”
2. File > Build and Run
3. Resize Player window rapidly
Expected result: The Player window gets resized
Actual result: Player freezes
Reproducible with: 2022.1.24f1, 2022.2.1f1, 2023.1.0a23
Could not test with: 2020.3.42f1 (No Silicon Editor), 2021.3.16f1 (build fails)
Reproducible on: macOS Ventura 13.0.1 (M1 Max)
Not reproducible on: macOS Ventura 13.0.1 (Intel), Windows 10
Comments (1)
-
unity_D7C7E93E160F73909BC2
Feb 13, 2023 17:42
This also happens in Unity 2021.3.15f1
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
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.