Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.3.X, 2018.1.X
Votes
0
Found in
2017.3.0f2
Issue ID
977003
Regression
No
PackedMemorySnapshot: Unable to resolve typeDescription of GCHandle.target
Reproduction steps:
1. Download user's attached project and open in Unity
2. Open scene "Scene"
3. Open BugReport -> Open TestCode Window
4. Click Capture Memory 'Editor'
Expected: No errors in console
Actual: Errors in console (view picture)
Reproduced on: 2017.3.0a6; 2017.3.0p1; 2018.1.0b1
Note:
These are error messages from the provided test case and not Unity error messages.
Some GCHandle's cannot be used to resolve the type. With pretty much every restart of the Unity editor, the fail-reason for that is different. Sometimes it outputs "Cannot find memory section of vtableClassPointer", sometimes it outputs "pointer is NULL".
Memory Snapshots introduced only from 2017.3.0a6.
Fixed in: 2018.1.0b9, 2018.2.0a1
Comments (2)
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
- [iOS] Application.deepLinkActivated does not get invoked while app is running when UIApplicationSceneManifest is added in Info.plist
- Inspector scroll area stretches when using components with nested serialized arrays on FBX model prefab instances
- Crash on ConstraintProjectionTree::projectionTreeBuildStep when ConfigurableJoint uses JointProjectionMode.PositionAndRotation and connected Rigidbody switches from kinematic to non-kinematic
- ScriptableObject asset is accessed during the lookup of Build Profiles when opening the Build Profiles Window
- [Multiplayer TPS Sample] Grenade launcher explosion misses the Player when the Collider count exceeds HitColliderBuffer
lukaszunity
Jan 04, 2018 07:48
This is a bug in Mono where it has a few GC handles that point to invalid objects and they should removed from the list of GC handles. The the invalid GC handles can be ignored for now, as they have no affect on the captured snapshot.