Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.6.0b10
Issue ID
886135
Regression
Yes
Taking detailed memory sample of player in profiler spams errors
How to reproduce:
1. Open the attached project
2. Build and run on Android, iOS or Standalone... (in 32 bits)
3. Make sure that Autoconnect profiler is enabled
4. When player runs select Memory part in profiler
5. Switch simple to detailed and take a sample
Result: sample is not taken and Unity shows two errors:
-Assertion failed on expression: '*current_offset==OBJECT_MEMORY_STREAM_TAIL'
-IndexOutOfRangeException: Array index is out of range
Reproducible: 5.6.0b10, 2017.1.0a2
Not reproducible: 5.5.2p1, 5.6.0b9
Comments (1)
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
- The cursor moves into wrong place when renaming folder/asset
- Assertion error "(dx - width < padding) || (dy - height < padding)" when using Pack Preview
- [Memory Profiler] The EntryType.NativeAllocationSites_MemoryLabelIndex of snapshots only reports -1 or 0 instead of the MemLabel used for allocations made from any call site.
- [Vulkan] Artifacts appear in the Player when using Screen Space shadows with orthographic camera
- Errors OnGUIDepth changed & GUIUtility:ProcessEvent when opening Textures with Third Party App
solovina
Apr 20, 2017 06:45
I meet the same problem.The version is 5.6.0f1.Does anybody can solve this?