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
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
Add comment