Search Issue Tracker
Fixed
Fixed in 1.0.0-pre.1
Votes
0
Found in [Package]
0.7.0-preview.2
0.7.1-preview.1
Issue ID
PROFB-27
Regression
No
Wrong number of objects or allocations shown when comparing Snapshots
Reproduction steps:
1. Open the user's attached project "TestMemoryProfiler2.zip"
2. Open the Memory Profiler window
3. Open the "Compare Snapshots" tab and select the both of the Snapshots
4. Open the "Objects and Allocations" tab
5. Select the "Diff All Native Objects" Table View and set Sort Descending by Size
6. Observe 3 rows of a texture named "Raw_mangheji" (2.7MB)
7. Open the "Single Snapshot" tab
8. Repeat steps 4-5
9. Observe 1 row of a texture named "Raw_mangheji" (2.7MB)
Expected result: The number of texture instances is the same at steps 6 and 9
Actual result: The number of texture instances is different
Reproducible with: 0.7.0-preview.2 (2020.3.37f1, 2021.3.7f1), 0.7.1-preview.1 (2022.1.10f1, 2022.2.0b2)
Not reproducible with: 1.0.0-pre.1 (2022.2.0b2), 1.0.0-pre.3 (2023.1.0a4)
Reproducible on: macOS 12.4
Note: also reproducible with "AutoMPG.RootSerializer.ISerializer" (0.5MB) under "Diff All Managed Objects"
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Resolution Note (fix version 1.0.0-pre.1):
Fixed in: 1.0.0-pre.1