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
- DisplayDialogComplex crashes with a long content string containg Cyrillic chars
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
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