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
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
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