Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.5.0b10
Issue ID
848508
Regression
No
Profiling editor leaks memory when selecting frame from the profiler graph
Reproduction steps:
1. Open a new project
2. Open the Profiler
3. Enable "Profile Editor"
4. Click on the graph so the information about the frame is shown
-Observe the memory increase with every click on the graphs
Note: Alternatively it is possible to reproduce the issue by clicking and dragging the mouse around the graph.
Note: Memory profiler shows that TextMesh memory is not cleared
Reproduced on: 5.6.0a2, 5.5.0b11, 5.4.2p4, 5.3.7f1, 5.2.5f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment