Search Issue Tracker
Fixed
Fixed in 1.1.1
Votes
0
Found in [Package]
1.1.0
Issue ID
PROFB-223
Regression
No
Memory Profiler - ArgumentOutOfRangeException: startIndex is out of range at 1000 on a length of 512
When using the Memory Profiler the following error is logged when making a certain selection
{code:java}
ArgumentOutOfRangeException: startIndex is out of range at 1000 on a length of 512
Parameter name: startIndex
{code}
Steps to reproduce:
1. Load in attached Capture
[^Blank_6000_2024-05-08_14-23-23.zip]
2. Go to item highlighted in Red
!image-2024-05-08-14-48-07-234.png|thumbnail!
3. Notice the error logged
Not reproducible with versions:
Can’t test with versions:
\\
Tested on (OS):
\\
Notes:
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
- Texture Sampling overlap causes graphical errors on specific Graphics APIs and Devices when using Framebuffer Fetch
- [Android] AssetBundle loading performance degradation when loading from a local Assetbundle
- [iOS][Android] Reflection with Generic Class returns unexpected values
- Shader Variant Collection Asset UI is hard to read when multiple Shaders and keywords are added
- Regression for "WebGL build is missing "malloc" and "free" functions when passing "-sERROR_ON_UNDEFINED_SYMBOLS=0" to emscriptenArgs"
Resolution Note (fix version 1.1.1):
ArgumentOutOfRangeException should no longer appear when opening certain snapshots