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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
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.