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
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
Add comment