Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.3.0b1
2019.1.0a3
Issue ID
1086540
Regression
Yes
Profiling Editor keeps leaking memory
Steps to reproduce:
1. Open new project
2. In Profiler window click "Profile Editor"
3. Let it run and while looking at the Task Manager and Unity's Memory usage
4. Memory usage keeps increasing.
5. Click on the timeline to show how many frames are existing in total
6. Profiler shows all of the frames being saved even though you can't even look up their information, because profiler only shows the last x amount of frames.
Expected: Either clear the unusable frames or allow to view them
Actual: Lots of frames are still being saved even though you can't observe their information
Reproduced on:
2018.3.0b4 , 2018.3.0b1
Version 2019.1.0a3 (0e3c7820a690)
Sun, 30 Sep 2018 14:48:41 GMT
Branch: trunk
Not reproduced on: (Memory doesn't pile up while profiling editor or only a little bit)
2017.4.12f1, 2018.1.0f1, 2018.1.9f2, 2018.2.11f1, 2018.3.0a5, 2018.3.0a7, 2018.3.0a11,
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Add comment