Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Shared-storage topics are never freed: streaming leaks ~32 frames per page load

未關閉
  • 哪裡不對？
#4,010 0 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 2 天內回覆

@T4rk1n 已經在處理了。

開始於 2026年9月24日。

評估

這個 Issue 還沒有評估資料。

描述

bug P1 size: 3

Describe the bug

Shared-storage pub/sub topics are never removed. The streaming transport (#3930/#3931) uses one topic per page load (stream_topic(connection_id) in dash/_stream_hub.py), and each topic keeps its last buffer_size (default 32) frames. So every page load that runs a streaming callback leaves its last 32 frames in memory for the life of the process.

With LocalSharedStorage, StoreEngine._topics (dash/_shared_storage/_engine.py) is a plain dict. _topic() adds an entry on first publish, head_seq or poll, and nothing ever deletes one. Pub/sub is not persisted, so the only thing that frees them is the owner process exiting.

Measured

A streaming callback yielding 40 frames of ~50 KB, driven headless with dash_duo: 20 page loads, then the browser navigates away and we wait 40s (past DOWNLINK_GRACE and POLL_GRACE).

  • 20 _dash_stream: topics still in engine._topics
  • 640 frames still buffered (32 per topic)
  • heap grew 39.9 MB, about 2 MB per page load

A long-running app streaming figures or LLM output grows without bound.

Other backends

  • DiskcacheSharedStorage: ss:seq:<topic> / ss:msg:<topic>:<n> are written without expire. Bounded only by the cache size_limit eviction.
  • RedisSharedStorage: the seq counter and stream keys have no TTL. MAXLEN limits messages per topic, not the number of topics.

App code using ctx.shared_storage.publish/subscribe with per-session or per-run topic names leaks the same way (about 2.4 KB per empty topic on the local engine).

Expected behavior

A topic nobody uses any more is released. Some options:

  • Local engine: drop a topic once it has no subscribers or waiters and has been idle past some window.
  • Add delete_topic(topic) to BaseSharedStorage and call it when a Downlink connection is finished (the pump already knows when the browser is gone).
  • A topic ttl, matching set(..., ttl=): Redis EXPIRE, diskcache expire=, a deadline in the local engine.

Streaming and shared storage are not released yet (4.5.0rc0), so this can be fixed before 4.5.0.

Repro

import asyncio
from dash import Dash, Input, Output, html

app = Dash(__name__)
app.layout = html.Div([html.Button("go", id="btn"), html.Div(id="out")])

@app.callback(Output("out", "children"), Input("btn", "n_clicks"),
              prevent_initial_call=True)
async def cb(n):
    for i in range(40):
        await asyncio.sleep(0.01)
        yield "x" * 50_000 + f"-{i}"
    yield "done"

Load the page and click the button N times across reloads, then inspect app.shared_storage._coord.engine._topics: one _dash_stream:<connection_id> entry per page load, each holding 32 frames, long after the browser left.

主要語言
Python
星號
24.4k
分支
2.3k
平均合併
1 天 20 小時
30 天內合併 PR
21

環境準備

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

plotly/dash 的其他 Issue

查看 plotly/dash 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。