Search Issue Tracker
Fixed
Fixed in 1.1.0-pre.2
Votes
0
Found in [Package]
1.0.0
Issue ID
PROFB-54
Regression
No
Memory Profiler "Select In Editor" selects the wrong asset
How to reproduce:
1. Open the attached user project “com.unity.multiplayer.samples.coop.zip“
2. Open the Memory Profiler window (Window>Analysis>Memory Profiler)
3. Select the “Boss Room Android (Base)” Snapshot
4. Select the “Unity Objects“ tab
5. Expand the “Texture2D“ dropdown menu
6. Select any “Font Texture“ Texture2D (except where the Font is “Roboto-Bold“)
7. Press “Select in Editor“
Expected result: The correct Texture2D is selected in the Editor
Actual result: The wrong Texture2D is selected in the Editor
Reproducible with: 1.0.0 (2022.1.23f1, 2022.2.0f1, 2023.1.0a20)
Can’t test with: 2020.3.42f1 (“CS8124: Tuple must contain at least two elements. error“ error in the Console), 2021.3.14f1 (“This feature is not available in Unity 2021.3.14f1” appears when trying to access the “Unity Objects“ tab)
Reproduced on: macOS 12.5 (Intel)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on SerializedProperty:CopyInternalImpl when clicking on a specific Asset
- Crash on BurstCompilerService::CompileAsync when opening a specific project
- [Android] Particles aren't rendered when the shader "Particle/Standard Unlit" or "Particles/Standard Surface" is used on a Material
- Crash on nvoglv64.dll when opening a project
- [RenderGraph] [CameraStacking] Passes are failing when CameraStacking and RG are enabled
Add comment