Search Issue Tracker
Fixed in 2019.2
Fixed in 2019.1
Votes
8
Found in
2019.1.0a5
2019.1.0a10
Issue ID
1105332
Regression
Yes
CanvasScaler.Update() allocates Memory every frame
To reproduce:
1. Download attached project “アーカイブ.zip" and open in Unity
2. Open “SampleScene” scene
3. Enter to Play mode
4. Open Profiler
5. Search for CanvasScaler.Update()
Expected results: In CanvasScaler.Update() GC Alloc shows that there is 0 B Memory allocated
Actual results: In CanvasScaler.Update() GC Alloc shows that there is 64 B Memory allocated
Notes:
- This issue appears on both Windows (Editor and Standalone), macOS (Editor and Standalone), iOS and Android
Reproduced on Unity 2019.1.0a5 and 2019.1.0a13
Not reproduced on Unity 2018.3.2f1 and 2019.1.0a4
Regression on Unity 2019.1.0a5
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
- [IL2CPP] UnityLinker error when building
- [macOS] VideoPlayer.clockTime gets stuck for a few frames when starting to play a video
- VideoPlayer.StepForward() does not VideoPlayer.OnFrameReady when using a non-transcoded video
- [Android] A few frames of audio is played when VideoPlayer.Prepare() is called with audio output mode set to Audio Source
- [Android] Audio is only stopped after a delay when VideoPlayer.Pause() is called
Wei-Lin-D
Jan 11, 2019 03:44
I also noticed this problem.
The Profiler says there is always 64B memory kept in CanvasScalar.Update().
Waiting for fix.
Wei-Lin-D
Jan 11, 2019 03:40
I also noticed this problem.
The Profiler says there is always 64B memory kept in CanvasScalar.Update().
Waiting for fix.
Wei-Lin-D
Jan 11, 2019 03:35
I also noticed this problem.
The Profiler says there is always 64B memory kept in CanvasScalar.Update().
Waiting for fix.