Search Issue Tracker
By Design
Votes
0
Found in
2022.1.0a16
Issue ID
1413145
Regression
Yes
CPU Total Allocated Memory is 250MB higher while baking with the Progressive Lightmapper
Steps to reproduce:
1. Open the attached reproduction project
2. Run the test "MemoryProfileTest" through the TestRunner (Window>General>TestRunner)
3. Open the Performance Test Report (Window>Analysis>Performance Test Report)
4. Notice the increase in memory usage ("Total Allocated Memory")
Analysis here: https://docs.google.com/spreadsheets/d/1wGQ6bQ7UBX_PlQYlxpRL89iDnQ1HY8A29FBbSsQlMXs/edit?usp=sharing
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
This is an optimization on how the files are written to disk to avoid unnecessary write-read-write of the same data, thus it requires more memory. It also comes with a major speed improvement.