Search Issue Tracker
Feature Request
Feature Request in 0.5.X
Votes
0
Found in [Package]
0.5.0-preview.1
Issue ID
PROFB-4
Regression
No
Snapshot screenshots take up an unreasonable amount of memory
Reproduction steps:
1. Create a new project and install the Memory Profiler package
2. Enter Play mode
3. Open the Memory Profiler (Window > Analysis > Memory Profiler)
4. Click "Capture"
5. Select the Snapshot in the Snapshot Panel and observe memory usage in Activity Monitor or Task Manager
Expected result: The screenshots are compressed so they take up less memory
Actual result: The screenshots aren't compressed and take up too much memory
Reproducible with: 0.4.4-preview.2 (2022.2.0a5), 0.5.0-preview.1 (2019.4.36f1, 2020.3.29f1, 2021.2.12f1, 2022.1.0b9, 2022.2.0a5)
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
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
- Shader Graph template titles blink and render incorrectly in “Create New Shader Graph Asset” window
- Profiler Captures List foldouts do not open when clicked on the foldout title
- Profiler Captures List date title is not centered vertically
Resolution Note:
Requires feature assessment - potential overlap with snapshot opening workflow changes
Resolution Note (0.5.X):
Requires feature assessment - potential overlap with snapshot opening workflow changes