Search Issue Tracker

Fixed

Fixed in 2022.3.68f1, 6000.0.59f1, 6000.2.6f1, 6000.3.0b1

Votes

62

Found in

2022.3.66f1

6000.1.16f1

6000.2.0f1

6000.3.0a4

Issue ID

UUM-113839

Regression

Yes

Memory leak warnings are thrown when creating a Particle System GameObject

-

Steps to reproduce:

  1. Create a new Unity project using the Universal 3D template
  2. Create a new Particle System (GameObject > Effects > Particle System)
  3. Observe the Console window

Actual results: Memory leak warnings are thrown

Expected results: No warnings or errors thrown

Reproducible with versions: 6000.0.58f1, 6000.1.15f1, 6000.1.16f1, 6000.2.0f1, 6000.3.0a4

Not reproducible with versions: 6000.0.54f1, 6000.1.14f1

Tested on (OS): Windows 11, macOS Silicon Sequoia 15.5

Notes:

  • Also reproduces in HDRP
  • Sometimes need to wait a bit after creating the Particle System for memory leak warnings to appear or click on other GameObjects

Comments (44)

  1. Player7

    Sep 09, 2025 22:43

    I get a ton of these showing in a game build with 6.2 .2f1 and seems to be caused by particles, if no particle used no errors...

    Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
    To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
    Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
    To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
    Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
    To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
    Invalid memory pointer was detected in ThreadsafeLinearAllocator::Deallocate!
    Invalid memory pointer was detected in ThreadsafeLinearAllocator::Deallocate!
    Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
    To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
    Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
    To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.

  2. Gokayy1

    Sep 09, 2025 19:47

    Happens for me in 6000.2.1f1 Universal 2D

  3. Magician-Cirkus

    Sep 09, 2025 13:41

    Noticed the issue Using Unity 6000.2.2f1. URP.

  4. Yu960803

    Sep 08, 2025 16:16

    Happens for me in 6000.0.55f1

  5. Yu960803

    Sep 08, 2025 16:16

    Happens for me in 6000.0.55f1

  6. aanconale

    Sep 07, 2025 09:25

    This issue happened on Mac OS Sequoia 15.6.1 using URP with 6000.0.57f1

  7. kaminari_chisaki

    Sep 04, 2025 02:39

    this bug happen for 6000.0.56f1. and unity editor has crashed sometimes.

  8. briand127

    Aug 31, 2025 15:38

    Bug is in URP 3D 6000.2.2f1

  9. berkce

    Aug 29, 2025 19:08

    Started happening today in Unity 6.2 (6000.2.2f1) URP 3D when using particle system.

    Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak

  10. DD_Hieu_san

    Aug 28, 2025 07:11

    Happens in Unity 6.2 (6000.2.1f1) URP 3D when using particle system.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.