Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
0
Found in
2017.3.0f3
Issue ID
987839
Regression
No
PackedMemorySnapshot: Unexpected connections between native objects
To reproduce:
1) Open attached user project
2) Build a Standalone Windows 64bit Player
3) Start Player
4) Make sure the Profiler is connected to the Player
5) Open MainMenu > BugReport > Open TestCode Window
6) Click "Capture Memory" button
Observe the MonoBehaviour "__MyTestGameObject" references not only "PlayerHealth", but also a lot of other objects that "PlayerHealth" and references of "PlayerHealth" reference.
Reproduced in 2017.1.0f3, 2017.3.0f3, 2018.1.0b4
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note (fix version 2020.1):
This bug was originally closed as By Design, as the system was indeed designed like that back then. It has been overhauled to only report direct connections and not indirect connections afterwards, which landed on 2020.1.0a11 and got backported to 2019.3.0b9. Connection tracking has subsequently seen a significant bug fix that landed on/got backported to 2021.2.0a12, 2021.1.9f1, 2020.3.12f1, and 2019.4.29f1.
This should therefore no longer be an issue, on any of the Unity Versions that are still supported.