Search Issue Tracker
By Design
Votes
0
Found in
5.6.2p4
Issue ID
973665
Regression
No
Profiler detailed memory object reference is endlessly recursive
To reproduce:
1. Open a new Unity project
2. Open Profiler window
3. Go into Play mode
4. Select Memory profiler
5. Choose Detailed instead of simple
6. Click "Take Sample: Editor"
7. Highlight "Gather object references"
8. Go to Builtin Resources --> Mesh --> Sphere
9. In the "Referenced By:" column, try to expand Sphere(MeshFilter)
Result: Endless recurssion, not possible to get to the deepest child (see attached gif "recursive.gif")
Reproduced on: 5.6.4p1, 2017.1.2p3, 2017.2.0p3, 2017.3.0b11, 2018.1.0a6
Note: Sphere is just an example, the same bug occurs with any selected object.
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
Add comment