Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0f1
Issue ID
975832
Regression
No
PackedMemorySnapshot: Missing connections between native objects
To reproduce
- Open attached user project
- Open Assets/Scene.unity
- Open in top menu bar "BugReport > Open TestCode Window"
- Click Capture Memory
Expected: Notice the GameObject "QQQ Cube" references all its Components.
- Build & run a Windows Standalone build
- Connect profiler to Windows Standalone build
- Open in top menu bar "BugReport > Open TestCode Window"
- Click Capture Memory of Standalone build
Actual: Observe the GameObject cannot be found and most other connections are missing too.
Reproduced in 2017.1.0f3, 2017.2.0f3, 2017.3.0f1, 2018.1.0a7
Comments (1)
-
Peter77
Dec 06, 2017 16:27
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2019.3.X):
The difference between Edit mode and Playmode/Standalone is that a component's managed representation exists only if said component has been requested by a script or in the case of PlayMode by the inspector. This is one of the main reasons for caching GetComponent<T>() calls in unity so that we create the managed representation of the native object only once.