[Bug]: When using the API to study, the error "Invalid state: Controller is already closed" appears.

[zhoufei0622]

Bug Description

Error during stream execution: TypeError: Invalid state: Controller is already closed
at Object.start (.next/server/app/api/research/route.js:15:680) {
code: 'ERR_INVALID_STATE'

Steps to Reproduce

1.使用GET/POST方式以API形式进行研究
2.偶尔出现Invalid state: Controller is already closed

Expected Behavior

正常结束

Screenshots

No response

Deployment Method

• Docker
• Vercel
• Server

Desktop OS

No response

Desktop Browser

No response

Desktop Browser Version

No response

Smartphone Device

No response

Smartphone OS

No response

Smartphone Browser

No response

Smartphone Browser Version

No response

Additional Logs

大佬，这种controller已被关闭错误偶尔会出现的原因是什么？应该如何解决呢？

[Amery2010]

Invalid state: Controller is already closed

Because the system may still hang after processing the data, I called controller.close() to manually terminate the SSE data stream after processing the data.

[teebu]

If its SSE, sounds like something I identified here #120 (comment)

[zhoufei0622]

在try——catch--finally中，在finally中最后执行controller.close()还是会出现这个问题。请问一下这是什么原因造成的。

…

------------------ 原始邮件 ------------------ 发件人: ***@***.***>; 发送时间: 2025年8月1日(星期五) 中午1:22 收件人: ***@***.***>; 抄送: ***@***.***>; ***@***.***>; 主题: Re: [u14app/deep-research] [Bug]: API方式进行研究时，出现Invalid state: Controller is already closed (Issue #124) 阿默里2010发表评论（u14app/深度研究#124） Invalid state: Controller is already closed 因为处理完数据后系统可能还是挂起的，所以我在处理完数据后调用手动终止SSE数据流。controller.close() — 直接回复此电子邮件、在 GitHub 上查看或取消订阅。 您收到此消息是因为您创作了线程。Message ID: ***@***.***>

[Amery2010]

This is an operation reserved for releasing server resources when the API was designed. It has caused interference to you. I will remove this design in subsequent versions.

[zhoufei0622]

如果是 SSE，听起来像是我在这里确定的东西 #120 （评论）

请问该问题解决了吗

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

If it's SSE, it sounds like something I'm sure of here #120 (comment)

Is this problem solved?