Search Issue Tracker
Fixed in 4.6.2
Votes
0
Found in
4.6.0f3
Issue ID
660156
Regression
No
[CanvasScaler] Editor freezes when entering first digit in X field of Reference resolution
To reproduce:
1. Open attached project
2. Open PentatonicScale scene
3. Select canvas
4. Change UI Scale mode to Scale with screen size on Canvas Scaler component
5. Highlight (select) X value
6. Try to enter 400
7. Once 4 is entered editor freezes for 10-15 minutes
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
murkantilism
Mar 07, 2016 04:53
Much thanks Ted23, just hit this bug in v5.2.1f1 when modifying X value of Ref. Resoltion, disabling scalar worked like a charm!
SkyArchitect
Mar 01, 2016 02:40
I've encountered the same issue on 5.3.2. And that cause my Windows to shut down and never be able to restart computer again. Please Help!
firestorm713q
Feb 01, 2016 23:23
This appears to still be present in 5.3.2
EMOTION THEORY
Nov 05, 2015 00:01
Any idea of the cause? In the same project this worked fine for me and now suddenly it doesn't.
EMOTION THEORY
Nov 05, 2015 00:00
Also confirming this exists in 5.2.1f1 when I change the Y value of the Reference Resolution in the CanvasScaler.
Just FYI, Ted23's workaround worked for me too:
1. disable the canvas scaler
2. change the X and/or Y values
3. enable the canvas scaler
snugsound
Oct 25, 2015 15:30
FYI I'm still encountering this issue in 5.2.1f1, can this be reopened?
JamesT
Jul 27, 2015 17:22
TED23's workaround worked for me as well.
ClaymoreCP
Jun 30, 2015 20:44
4.6.5, still having this issue.
x70x
May 27, 2015 22:17
I'm using 4.6.2 and this is not fixed
Apolyon6k
Feb 04, 2015 21:12
I am on Version 4.6.2f1 and the issue is still there, not fixed!