TEN-framework / TEN-framework/ten-framework

[BUG] Memory leak when new sub graph created and destroyed.

Open
#2,079 0 comments 0 reactions 1 assignee View on GitHub

@sunxilin is already working on this.

Since Mar 2, 2026.

bug
Dominant language
Python
Stars
11.1k
Forks
1.4k
Avg merge
2d 15m
Merged PRs (30d)
22

Description

Description

As title. Maybe there are some leaks on Rust code.

Environment

Linux

Steps to reproduce

Start a graph then stop it. Repeat for multiple times.

Expected behavior

The memory usage should not increase after starting and stopping graphs for multiple times.

Severity

Critical

Additional Information

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.