Search Issue Tracker
Fixed
Fixed in 2022.3.22f1
Votes
0
Found in
2022.3.21f1
Issue ID
UUM-65871
Regression
Yes
Memory is leaking when toggling a GameObject with a Light Component and Entities Graphics is used
How to reproduce:
1. Open the “GraphicsTempJobLeak“ project
2. Open the “Main” scene
3. Make sure that the Scene view window is opened
4. In the Hierarchy window select the “Spot Light” GameObject
5. In the Inspector window enable the “Spot Light” GameObject
6. Observe the Console
Expected result: No warnings regarding “JobTempAlloc” are thrown
Actual result: The “Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak” warning is thrown
Reproduced with: 1.0.16, 1.2.0-pre.12 (2022.3.16f1, 2022.3.21f1)
Not reproduced with: 1.0.16, 1.2.0-pre.12 (2022.3.15f1, 2023.3.0b10)
Reproduced on: Windows 10 (by reporter), Windows 11
Not reproduced on: No other environment tested
Note: Reproducible in the Player
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Add comment