Search Issue Tracker
Fixed in 0.2.7-preview.1
Votes
0
Found in [Package]
0.2.5-preview.1
Issue ID
1276377
Regression
No
[Memory Profiler] Orange highlight shows different data when changing its position and then returning it to default
How to reproduce:
1. Open the attached project "case1276377.zip"
2. Open Memory Profiler window
3. Open snapshots called "1" and "2"
4. Click Diff at the bottom of the Memory Profiler window
5. Change the view drop-down to 'Memory Map Diff'
6. Observe tiny orange highlight next to the 1st address, also observe the data in the bottom table
7. Click anywhere on the 1st address
8. Click back to where to original orange highlight was
10. Observe the data in the bottom table
Expected result: Snapshot table shows the same data when highlight backs to its default position
Actual result: Snapshot table shows no data when highlight backs to its default position
Reproducible with: 2018.4.27f1, 2019.4.11f1, 2020.1.6f1, 2020.2.0b3
Reproducible with package versions: 0.1.0-preview.2, 0.2.5-preview.1
Could not test with package versions: 0.1.0-preview.1 (Memory profiler window layout is different)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Add comment