Search Issue Tracker
Fixed
Under Consideration for 6000.0.X
Votes
0
Found in
6000.0.57f1
Issue ID
UUM-116910
Regression
Yes
Memory leak when a lot of Particle Systems instantiated while Profiler is open
How to reproduce:
1. Open the attached project "IN-113314"
2. Open the Profiler window
3. Enter Play mode
4. Wait for several minutes (~2-3 minutes)
5. Observe the Console window
Expected result: No memory leak warnings in the Console window
Actual result: Several memory leak warnings in the Console window
Reproducible with: 6000.0.55f1, 6000.0.57f1,
Not reproducible with: 2023.1.0a1, 6000.0.54f1(4c506e5b5cc5), 6000.2.3f1, 6000.3.0b1
Reproduced on: Windows 11, macOS 15.6 (M1),{color:#ffffff} {color}macOS 24.3.0 (arm64) (by user)
Not reproduced on: No other environment tested
Notes:
-Warning: “Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak“
-Sometimes this error occurs: "Invalid memory pointer in ThreadsafeLinearAllocator::Deallocate!", but it's not consistent.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note:
Fixed by another internal issue: UUM-113729: Performance regression caused by PR "Merge PR #71427 from graphics/particles/fix/uum-103773-geometry-job-crash"