Quick answer: Sub-emitters referencing themselves (or forming a cycle with siblings) create exponential particle growth. Audit each sub-emitter reference chain, cap Max Particles per system, and reduce Inherit Lifetime to break the compound.

Here is how to fix Unity particle system sub-emitter infinite loop. You author a fireworks effect: main system spawns “rockets,” rockets spawn sparks on death via a sub-emitter. You hit play and watch a single firework launch — within a few seconds your frame rate dies and the game window fills with particles. You check Max Particles — set to 10,000. All used. The sub-emitter is eating itself.

The Symptom

Particle counts grow without bound. Frame rate drops as the simulator struggles with hundreds of thousands of active particles. Max Particles counts hit limit quickly. Visual: screen filled with explosions cascading outward. In the editor, the Particle System preview shows absurd particle counts despite a reasonable per-system burst value.

What Causes This

Self-referential sub-emitter. System A’s death sub-emitter is System A itself. Each dying particle spawns more A particles, each of which eventually dies and spawns more. Geometric growth.

Cyclic reference between systems. System A sub-emits System B. System B sub-emits System A. Each death triggers the other, forever. Harder to spot because the cycle spans two assets.

Inherit Lifetime multiplier compounding. Sub-emitter Inherit Lifetime at 1.0 means child lifetime = parent’s remaining lifetime. A 10-second rocket spawns 10-second sparks on death. Those sparks stay alive a long time, each of which spawns more particles during their lives if a Birth sub-emitter is configured — pile-up.

Burst with Emit Probability 1 and high particle counts. A sub-emitter with 50 particles per burst triggered by each death of a 50-particle parent fires 2500 children on the first generation. Chain to a second-level sub-emitter and you get 125,000 particles in a frame.

The Fix

Step 1: Audit sub-emitter references. For every Particle System with the Sub Emitters module enabled:

  1. Note the Particle System referenced in each sub-emitter slot
  2. Draw a directed graph: A -> B -> C (if A spawns B, B spawns C)
  3. Verify no cycles (A -> A or A -> B -> A)

Break any cycle by making the last system in the chain have no sub-emitters.

Step 2: Cap Max Particles as safety net. In each Particle System’s main module, set Max Particles to a reasonable cap:

Once the cap is hit, new particles do not spawn. Your effect looks truncated but performance does not collapse. Good safety net for when the artist (or code) pushes burst values too high.

Step 3: Tune Inherit Lifetime. On the sub-emitter module, each sub-emitter entry has an Inherit properties section. Set Inherit Lifetime to 0 (child uses its own startLifetime) or a small value like 0.3 (child gets 30% of parent’s remaining life).

Without inheritance, children live their own lifetime and die predictably. With high inheritance, children can outlive the original burst and keep triggering sub-emitters for seconds.

Step 4: Limit per-burst count. Sub-emitter bursts are multiplied by how many parent particles die. If you want 100 sparks per rocket and 10 rockets, do not set the sub-emitter burst to 100 (which would fire 100 per rocket = 1000 total). Instead:

Each rocket death fires 10 sparks. 10 rockets * 10 sparks = 100 sparks. Manageable.

Debugging Live Counts

Select the main effect in the scene during play. The Particle Effect panel shows live counts per system. Watch particle counts as the effect plays. Exponential growth visible here is the smoking gun.

You can also log counts from code:

void LateUpdate()
{
    foreach (var ps in GetComponentsInChildren<ParticleSystem>())
    {
        if (ps.particleCount > 500)
            Debug.LogWarning($"{ps.name}: {ps.particleCount} particles");
    }
}

Understanding the issue

Particle systems are stateful machines. Each particle has its own lifetime, and the system has its own configuration. Bugs that involve the lifecycle (creation, death, pool reuse) tend to be timing-sensitive and hardest to reproduce.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Sub-emitters are multipliers. Without caps, any cycle becomes exponential. Cap Max Particles; audit references; test long-running before shipping.”

Related Issues

For particle stop issues, see Particle Stop Not Stopping Immediately. For lit particle flickering, Lit Particle Flickering covers related effects bugs.

Draw the reference graph. Cap Max Particles. Inherit Lifetime low. No cycles.