Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0b1
Issue ID
1080586
Regression
Yes
In Profiler Window Memory tab, 'ProfilerSession' shows very high memory consumption when Profiler Window is filled up with data
How to reproduce:
1. Create a new Unity project
2. Open Profiler Window
3. Enter Play mode and wait until the whole Profiler window is covered with data (takes about 5 seconds)
4. Navigate to Profiler Window - > Memory tab and change data display mode from Simple to Detailed
5. In Profiler Window, press 'Take Sample: Editor'
6. In Profiler Window, inspect value located in Other -> Profiling () -> ProfilerSession
Expected result: ProfilerSession is about 30Mb
Actual result: ProfilerSession is about 3Gb
Reproducible with: 2018.3.0b1, 2018.3.0b2, 2019.1.0a1
Not reproducible with: 2017.1.5f1, 2017.4.11f1, 2018.2.8f1, 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
- “[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