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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment