Search Issue Tracker
Won't Fix
Won't Fix in 5.4.X, 5.5.X, 5.6.X
Votes
0
Found in
5.3.4p4
Issue ID
800658
Regression
No
Loading specific memory snapshot causes an exception in the memory profiler
Reproduction steps:
1. Download attached "MemorySnapshot3.memsnap" memory snapshot.
2. Download and Open attached "memoryprofiler" project.
3. Go to "Window > MemoryProfiler".
4. Click "Load Snapshot".
5. Select "MemorySnapshot3.memsnap" memory snapshot.
6. Wait for 5-15 minutes.
7. Notice the error in the console window:
ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: startIndex
System.BitConverter.PutBytes (System.Byte* dst, System.Byte[] src, Int32 start_index, Int32 count) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System/BitConverter.cs:176)
-
Sprarage
Dec 03, 2019 16:40
If bitbucket profiler is no longer supported by 2018.3 then at least this 2019.2 page needs update:
https://docs.unity3d.com/2019.2/Documentation/Manual/BestPracticeUnderstandingPerformanceInUnity2.html -
sirchb
Aug 12, 2016 23:49
I got this error while taking a memory snapshot of my game (not loading from a previously saved file). I managed to get my snapshot to technically work by changing this line:
for (int i = 0; i != arrayLength; i++)
To this:
for (int i = 0; i != arrayLength && cursor.offset < cursor.bytes.Length; i++)
in Crawler.cs
This stops the BytesAndOffset object from reading past the end of its byte array, which was happening when BytesAndOffset.pointerSize was 4.
Not sure if this actually solves the root problem but it let me see the snapshot and nothing noticeable was wrong with it.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
This case is no longer relevant as it targets the bit-bucket memory profiler which is unsupported. A new memory profiler was introduced in 2018.3.