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
- 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