Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.4.7f1
Issue ID
1269293
Regression
No
PackedMemorySnapshot: nativeObjects.gcHandleIndex contains -1 always
Capturing a PackedMemorySnapshot and inspecting the gcHandleIndex of a nativeObject, shows it contains -1 always. This can't be right, some nativeObjects should contain a valid gcHandleIndex.
Please see the attached video.
Reproduce
* Open attached project
* Open Unity Profiler and switch it to "Editor"
* Execute from main menu "BugReport > Capture Snapshot"
Actual
Observe in the Console window a message similar to "valid gcHandleIndices: 0, nativeObjects: 2195"
Expected
"valid gcHandleIndices" should not be 0.
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
- Shader Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
- Crash on RebuildTransformHierarchyOrMarkForDestruction when opening a scene
- The Editor hangs when opening a project that uses local packages and Version Control
- Area Light is culled when Camera Frustrum is outside the lights range
- The characters of the bottom option in the Scene View Debug Draw Mode dropdown menu are cut off
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0b1
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.4f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.10f1