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
- “STP” in Project window > Advanced Upscalers by Priority menu list is shown as available to add when it is already added to the list
- Rename fails with an error “Canceling DisplayDialog” when renaming a Mipmap Limit Group in Project Settings > Quality after adding a new group
- Obsolete API warning CS0618: 'HDAdditionalLightData.SetIntensity(float)' is thrown when installing “Output Event Helpers” Samples to the project
- Misaligned “Show Property Gizmo” and affected “Color” field in Inspector of a VFX Asset
- UIElements Style.translate is shifted down on the Y axis when in Play Mode
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.