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
- Double clicking script field no longer opens it in the external script editor
- [Android] Build fails with built-in PAD custom asset(s) when using sample Addressable
- [iOS] nw_read_request_report crash
- The serialized field value cannot be changed when trying to set it back to "None"
- The dropdown component breaks when the 31st Layer is 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.