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
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
- “ReferenceError: Pointer_stringify is not defined” error is thrown when downloading a file
- GameObjects are not rendered when using a fragment shader with RWStructuredBuffer in URP
Add comment