Search Issue Tracker
Fixed
Fixed in 1.1.0-exp.1
Votes
0
Found in [Package]
0.7.1-preview.1
1.0.0
1.1.0-exp.1
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Add comment