Search Issue Tracker
Fixed
Fixed in 1.1.0-pre.2
Votes
0
Found in [Package]
1.1.0-pre.1
Issue ID
PROFB-166
Regression
No
Memory Profiler tooltip for dropdown for changing the contributed memory type is hardcoded to the wrong Unity Version, should be 2022.3 or earlier
Reproduction steps:
1. Open the attached project “MemoryProfilerBug“
2. Open the Memory Profiler (Window>Analysis>Memory Profiler)
3. Select the snapshot “Ww1dev“
4. Select the Unity Objects tab
5. Try to access the contributed memory type list
Expected result: The tooltip information is accurate and shown correctly respective to the Unity Version the snapshot was taken from (Available for everything above 2023.1, Not available for older snapshots)
Actual result: The tooltip suggests the dropdown would be available for 2022 versions and as it is hardcoded to suggest that the snapshot is considered to be taken in Unity 2021.2 or older is misleading.
Reproducible with: 1.1.0-exp.1, 1.1.0-exp.2, 1.1.0-pre.1 (2022.3.4f1, 2023.1.3f1, 2023.2.0a22)
Couldn't test with: 1.0.0 (the option to change the memory type does not exist)
Reproducible on: Windows 11
Note: The issue is reproducible when snapshots are taken with Unity version older than 2023.1
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
- Multiple errors occur when setting the Render Object Event to AfterRenderingPostProcessing while using STP for Upscaling
- UnityYamlMerge.exe doesn't correctly handle merge conflicts in modified properties on a prefab variant
- Inconsistent color scheme in "Details" section of "Select Presets" inspector window
- Crash on __pthread_kill when launching Editor via command-line with "-disableManagedDebugger" argument
- [VFX] Deleting “New Group Node” name doesn’t allow to type or add new name
Resolution Note (fix version 1.1.0-pre.2):
This was already fixed in 1.1.0-pre.2