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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment