Search Issue Tracker
Fixed in 0.2.7-preview.1
Votes
0
Found in [Package]
2018.4
2019.3.9f1
2020.2
Issue ID
1237888
Regression
No
Memory Profiler scrambles the type and member variables referenced
Steps to reproduce:
1. Open a new project
2. Import "Snapshot-637218720955848055.snap" memory snapshot
3. Select Table -> All Managed Objects view
4. Type "Array3<System.Byte" in the type match search bar.
5. Press on the Refcount number on any of the given objects
Expected: the references point to Voxeland.EditBlock.typesGrid
Actual: VoxelandChunkWorkspace.typesGrid is linked as a reference, not only typesGrid is not a member of VoxelandChunkWorkspace, it also does not contain a member variable of type Array3<System.Byte>
Reproduced in: 2018.4.23f1, 2019.3.15f1, 2020.1.0b10, 2020.2.0a11
-
shubhamswaraj2021
Aug 21, 2020 05:48
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 0.2.7-preview.1):
Fixed in Memory Profiler 0.2.7-preview.1 and available from Unity version 2018.4.0f1 and above