Search Issue Tracker
Fixed
Fixed in 6000.0.X, 6000.3.X, 6000.4.X, 6000.5.0a1
Votes
1
Found in
6000.0.58f1
6000.3.0b4
6000.4.0a1
6000.5.0a1
Issue ID
UUM-121040
Regression
No
Memory spike after activating Freeform Light2Ds
Steps to reproduce:
1. Open the “IN-115290” project
2. Open the “SampleScene” scene
3. Enter Play Mode
4. Press the button in the middle and exit Play Mode
5. Copy ‘1.snap' and '2.snap’ in the root project folder to the MemoryCaptures folder
6. Open Memory Profiler to compare two snapshots
7. Observe “Malloc(Temp) Pool” in All Of Memory
Expected result: The memory is the same in both snapshots
Actual result: The memory in “snap-2” is ~70 mb higher
Reproducible with: 6000.0.58f1, 6000.1.16f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Testing environment: macOS 26.0 (M4 Pro), macOS 15.5.1 (M4 Pro) (by user)
Not reproducible on: No other environment tested
Notes:
- Also reproducible in iOS Player (Xcode memory allocation debug)
- The memory spike comes from Light2D_LateUpdate
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment