Search Issue Tracker
Fixed in 0.2.5-preview.1
Votes
0
Found in [Package]
2019.3.0a2
2019.4.1f1
2020.1
2020.2
Issue ID
1260533
Regression
Yes
Frame chart information of certain Profiler Modules disappear when opening a Memory Profiler Snapshot
How to reproduce:
1. Open user's attached "2019.4" project
2. Open the Profiler (Window->Analysis->Profiler)
3. Open the Memory Profiler (Window->Analysis->Memory Profiler)
4. In the Profiler window set the Profiler to record the Editor (press on the drop-down list at the left side in the Profiler controls and choose Editor)
5. In the Profiler window enable all of the Modules (at the top left corner of the Profiler window press on the Profiler Modules drop-down list and toggle all of the Modules)
6. Enable recording in the Profiler
7. In the Memory Profiler window open the "Snapshot-637293849486777128" Snapshot
Actual result: Frame chart information of all Profiler modules except GPU and Global Illumination disappear
Expected result: Frame chart information of all Profile modules do not disappear
Reproducible with: 2019.3.0a2, 2019.4.3f1, 2020.1.0b15, 2020.2.0a17
and any version of com.unity.memoryprofiler up to and including 0.2.4-preview.1
Not reproducible with: 2018.4.24f1, 2019.3.0a1
Notes:
- Profiler does not need to be recording for the Frame chart information to disappear when opening a Memory Profiler Snapshot
- Restarting Unity Editor fixes the issue
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 0.2.5-preview.1):
Fixed in: Memory Profiler 0.2.5-preview.1