Search Issue Tracker
Fixed
Fixed in 2021.3.49f1, 2022.3.58f1, 6000.0.38f1, 6000.1.0b6, 6000.2.0a3, 7000.0.0a20
Votes
2
Found in
2021.3.47f1
2022.3.56f1
6000.0.34f1
6000.1.0b1
6000.2.0a1
Issue ID
UUM-92512
Regression
No
Lights with Cookies generate Cookie Atlas and increase Memory usage every time when Play mode is entered
Reproduction steps:
1. Open the attached “My project.zip” project
2. Open the Memory Profiler Window (Window > Analysis > Memory Profiler)
3. Press “Capture New Snapshot”
4. Open the Snapshot and navigate to the ”Unity Objects” tab
5. Search for “Universal Light Cookie Atlas_4096x4096_B10G11R11_UFloatPack32_Tex2D”
6. Observe the amount of Objects
7. Enter the Play mode
8. Exit the Play mode
9. Repeat 2-6th steps
Expected result: “Universal Light Cookie Atlas_4096x4096_B10G11R11_UFloatPack32_Tex2D” number of files does not increase
Actual result: “Universal Light Cookie Atlas_4096x4096_B10G11R11_UFloatPack32_Tex2D” number of files and Memory usage increases every time Play mode is entered
Reproducible with: 2021.3.47f1, 2022.3.56f1, 6000.0.34f1, 6000.1.0b1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment