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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment