Search Issue Tracker
Fixed
Fixed in 1.1.0-exp.1
Votes
0
Found in [Package]
1.0.0
Issue ID
PROFB-66
Regression
No
“IndexOutOfRangeException: Index was outside the bounds of the array.” error when selecting "No Name" ScriptableObjects in the Memory Profiler
How to reproduce:
1. Open the attached user project “Bug Report.zip“
2. Open the Memory Profiler (Window>Analysis>Memory Profiler)
3. Select the “Snapshot-638067436652085695“ Snapshot
4. Select the “Unity Objects“ tab
5. Expand the “ScriptableObject” list
6. Scroll down until the four “<No Name>“ ScriptableObjects are found
7. Select one of them
Expected result: No error appears
Actual result: “IndexOutOfRangeException: Index was outside the bounds of the array.” error appears in the Console
Reproducible with: 1.0.0 (2022.2.2f1, 2023.1.0a25)
Can’t test with: 1.0.0 (2020.3.43f1, 2021.3.16f1) (“Unity Objects“ tab not implemented)
Reproduced on: macOS 13.0.1 (Intel)
Note: The error also appears when selecting other ScriptableObjects after selecting the “<No Name>“ ScriptableObject
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
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
- Graphics Compositor breaks Unity rendering when the "Output Camera" is changed to a scene Camera and one Camera SubLayer is active
- The Editor freezes on RenderGraphViewer.Repaint when entering too many characters in search fields without character limits
- Adding a new SubLayer in Graphics Compositor renders BaseLayer darker and makes it flicker
Resolution Note (fix version 1.1.0-exp.1):
fix in PR