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.
Comments (1)
-
Peter77
Jan 09, 2021 09:50
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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