Search Issue Tracker
Fixed
Fixed in 1.1.0-exp.1
Votes
0
Found in [Package]
0.7.1-preview.1
1.0.0
Issue ID
PROFB-79
Regression
No
Error is logged when selecting UnityEngine.Terrain element in Memory Profiler
Reproduction steps:
1. Open the attached project “MemoryProfilerBug”
2. Open the Memory Profiler “Window>Analysis>Memory Profiler”
3. Select the memory snapshot “Snap1”
4. Open the tab “All of Memory”
5. Expand the list items “Scripting Memory>Managed Objects“
6. Click on the list item “UnityEngine.Terrain“
7. Observe the Console Window
Expected result: No error is being thrown
Actual result: In the Console Window “Index was outside the bounds of the array” error is logged
Reproducible with: 0.7.1-preview.1 (2020.3.44f1, 2021.3.17f1, 2022.1.24f1, 2022.2.0b9), 1.0.0 (2022.2.3f1, 2023.1.0b1, 2023.2.0a3)
Reproducible on: Windows 11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment