Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
2017.1.0b6
Issue ID
913382
Regression
No
Profiler memory data labels overlay other parts of Profiler UI
Reproduction Steps:
1. Open new Unity project.
2. Enter Play mode in any scene.
3. Open Profiler window.
4. Wait until there are enough frames to fill up the Profiler.
5. Move the memory data bar to the far left of the Profiler.
Expected result: Profiler memory data labels are placed so that they would not overlay the Profiler UI.
Actual result: Profiler memory data labels overlay Profiler UI. (GIF attached)
Reproducible with: 5.4.5f1, 5.5.3p4, 5.6.1p1, 2017.1.0b6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment