bug: agent stops responding after multiple concurrent tabs
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 冷清
- 技术栈
- python, typescript
调研方向
Start with the deployed reproduction using three browser tabs, then inspect main.py, especially BoundedMemorySaver(max_threads=200) and the streaming request path. Check whether concurrent sessions, connection limits, rate limits, or unsurfaced backend errors explain the hang; done means independent tabs receive responses, and resource failures show an error instead of waiting silently.
由索引模型根据 Issue 内容生成。
描述
Bug
The agent stops responding when multiple browser tabs are open against the deployed app. On the third tab, the agent hangs after the user sends a message — no response, no streaming indicator, no error.
Steps to reproduce
- Open the deployed app in tab 1, send a message (e.g. "visualize a musical chart") — works fine
- Open tab 2, send a message — works fine
- Open tab 3, send a message (e.g. "I want to understand the difference between BFS and DFS...") — agent never responds
The UI shows the user messages and suggestion chips ("Try these Prompts") but no assistant response arrives. No loading indicator, no error state.
Screenshot
The chat shows:
- "visualize a musical chart"
- "Create a 3D animation of a sphere turning into an icosahedron..."
- "I want to understand the difference between BFS and DFS. Create an interactive comparison on a node graph."
None received a response. Suggestion chips are visible but the agent is unresponsive.
Possible causes
- Thread/session exhaustion — The agent uses
BoundedMemorySaver(max_threads=200)inmain.py. Multiple tabs may be creating separate threads that exhaust the pool or hit a concurrency limit. - WebSocket/SSE connection limit — The browser or server may be hitting a connection limit for streaming responses.
- LangGraph checkpoint contention — Multiple concurrent sessions writing to the in-memory checkpointer could cause deadlocks.
- OpenAI API rate limiting — Multiple concurrent requests to GPT-5.4 could hit rate limits with no visible error surfaced to the user.
- Missing error handling — The frontend may not surface backend errors, making it look like the agent is "thinking" forever.
Expected behavior
Each tab should operate as an independent session. If a resource limit is reached, the user should see an error message rather than silent failure.
Environment
- Deployed on Render
- Agent: LangGraph + CopilotKit middleware
- Model: GPT-5.4 via langchain_openai
- Checkpointer:
BoundedMemorySaver(max_threads=200)
- 主要语言
- TypeScript
- 星标
- 1.6k
- 派生
- 203
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
CopilotKit/OpenGenerativeUI 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 4/5 3-5 天 新手友好度 48/100
CopilotKit/OpenGenerativeUI#87 · 2 条评论 ·
-
难度 5/5 一周以上 新手友好度 35/100
-
难度 4/5 3-5 天 新手友好度 45/100
查看 CopilotKit/OpenGenerativeUI 的全部 Issue
相似的 Issue
-
难度 1/5 1-3 小时 新手友好度 88/100
supabase/agent-skills#611 ·
-
难度 1/5 1 小时以内 新手友好度 68/100
polka-codes/test#345 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 92/100
GoogleChromeLabs/project-sesame#217 ·
维护者通常 12 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
solana-foundation/solana-com#2202 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100