Skip to content

fix: release references to completed stage logics in GraphInterpreter#3030

Open
He-Pin wants to merge 1 commit into
mainfrom
fix/graph-interpreter-memory-leak
Open

fix: release references to completed stage logics in GraphInterpreter#3030
He-Pin wants to merge 1 commit into
mainfrom
fix/graph-interpreter-memory-leak

Conversation

@He-Pin

@He-Pin He-Pin commented May 31, 2026

Copy link
Copy Markdown
Member

Motivation

When multiple stages are fused, a single alive stage keeps the GraphInterpreter alive and with it references to all already completed GraphStage logics, which may keep a significant amount of memory.

This issue was originally reported in akka/akka-core#23439.

Modification

  • Modified GraphInterpreter.finish() to release references to all stage logics after finalization
  • Modified GraphInterpreter.toSnapshot() to handle null logics gracefully
  • Added null checks in finish() to avoid NPE when logic is already null

Result

GraphInterpreter no longer keeps references to completed stage logics, allowing them to be garbage collected even if the interpreter is still alive due to other fused stages.

Tests

  • Added directional test to verify logics are released after finish()
  • Added test to verify logics are released when stages complete early

References

@He-Pin He-Pin requested a review from Copilot May 31, 2026 20:29
@He-Pin He-Pin added this to the 2.0.0-M4 milestone May 31, 2026
@He-Pin He-Pin added the t:stream Pekko Streams label May 31, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR attempts to reduce GraphInterpreter memory retention by clearing stage logic references after finalization and adapting snapshots/tests for released logics.

Changes:

  • Clears entries from GraphInterpreter.logics during finish().
  • Adds null-aware logic snapshot handling.
  • Adds tests asserting the logics array is nulled after finish().

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File Description
stream/src/main/scala/org/apache/pekko/stream/impl/fusing/GraphInterpreter.scala Updates finalization and snapshot behavior for null stage logic entries.
stream-tests/src/test/scala/org/apache/pekko/stream/impl/fusing/GraphInterpreterSpec.scala Adds regression tests for releasing stage logic references.
Comments suppressed due to low confidence (1)

stream/src/main/scala/org/apache/pekko/stream/impl/fusing/GraphInterpreter.scala:757

  • toSnapshot still dereferences logicIndexes(connection.inOwner)/outOwner, but logicIndexes now excludes every released (null) logic. After finish() nulls logics, any snapshot of a shell that still has its connections array will throw NoSuchElementException instead of producing the <completed> snapshots added above. Use the owners' stable stageId to index logicSnapshots so released logics are handled.
    val logicIndexes = logics.zipWithIndex.collect { case (stage, idx) if stage ne null => stage -> idx }.toMap
    val connectionSnapshots = connections.filter(_ ne null).map { connection =>
      ConnectionSnapshotImpl(
        connection.id,
        logicSnapshots(logicIndexes(connection.inOwner)),
        logicSnapshots(logicIndexes(connection.outOwner)),

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +322 to +324
builder(GraphStages.identity[Int])
.connect(source, GraphStages.identity[Int].in)
.connect(GraphStages.identity[Int].out, sink)
Comment on lines +349 to +351
// Release reference to the stage logic so it can be garbage collected
// even if the GraphInterpreter is still alive due to other references
logics(i) = null
}
// Release reference to the stage logic so it can be garbage collected
// even if the GraphInterpreter is still alive due to other references
logics(i) = null
@He-Pin He-Pin requested a review from pjfanning June 16, 2026 10:01
Motivation:
GraphInterpreter retains strong references to completed stage logics in
the logics array, preventing garbage collection even after stages have
finished. This is especially problematic for long-running fused
interpreters that host subfused shells, where completed initial stages
remain referenced for the lifetime of the actor. Additionally,
Connection objects retain strong references to handler objects
(inHandler/outHandler), further preventing GC of completed stage logics.

Modification:
- afterStageHasRun now scans ALL logics for completed stages instead of
  only checking the single activeStage. This ensures stages that complete
  without being activeStage (e.g., boundary stages calling complete(),
  cascading completions) are properly finalized and released.
- finish() and afterStageHasRun null connection handlers (inHandler/
  outHandler) for finalized stages, breaking handler-to-logic reference
  chains to enable garbage collection.
- toSnapshot handles null logics gracefully with <completed> placeholder
  and uses connection.inOwner.stageId for positional indexing instead of
  identity-based map lookups that fail with NPE on null logics.
- inLogicName/outLogicName debug methods guard against null logics.
- finish() sets logics(i) = null after finalizing each stage.
- Fix GraphStageLogicSpec "not double-terminate" test to save logic
  references before execute() since afterStageHasRun now releases
  completed logics.

Result:
Completed stage logics are properly finalized and released for GC
during normal stream execution (not just in finish()), reducing memory
retention in long-running fused interpreters.

Tests:
- stream-tests/testOnly GraphInterpreterSpec: 13/13 passed (includes 2 new regression tests)
- stream-tests/testOnly GraphStageLogicSpec: 17/17 passed
- stream-tests/testOnly InterpreterSpec+LifecycleInterpreterSpec+InterpreterSupervisionSpec+GraphInterpreterFailureModesSpec: 54/54 passed

References:
None - memory leak fix
@He-Pin He-Pin force-pushed the fix/graph-interpreter-memory-leak branch from c58c59e to d29add0 Compare June 16, 2026 12:13
@He-Pin He-Pin removed this from the 2.0.0-M4 milestone Jun 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t:stream Pekko Streams

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants