[Feature Request]: 后台生成回答内容
Closed this issue · 5 comments
Problem Description
大佬，是这样，我输入问题后，切换到别的应用程序，离开当前页面，回答就不在继续生成了，只有切换回回答页面，回答才会继续
Solution Description
大佬后续是否考虑优化这个后台回答的功能，不然的话只能停留在当前页面等待回答完成
Alternatives Considered
No response
Additional Context
No response
Bot detected the issue body's language is not English, translate it automatically.
Title: [Feature Request]: Generate answer content in the background
Problem Description
Sir, this is it. After I enter the question, switch to another application and leave the current page, the answer will no longer continue to be generated. Only when I switch back to the answer page will the answer continue.
Solution Description
Will you consider optimizing the background answering function in the future? Otherwise, you can only stay on the current page and wait for the answer to be completed.
Alternatives Considered
No response
Additional Context
No response
这个应该不是代码层面的问题，而是浏览器的机制问题。据我所知，Chrome 浏览器（包括Chrome内核的所有浏览器），在离开当前页面后会进入半休眠状态（为了节约内存和cpu开销），半休眠状态下应该会出现您提到的这种情况。
您可以考虑试试 App 版本，App 版本使用的是独立内核，应该会避免进入半休眠状态
Bot detected the issue body's language is not English, translate it automatically.
This should not be a code-level problem, but a browser mechanism problem. As far as I know, the Chrome browser (including all browsers with Chrome core) will enter a semi-sleep state after leaving the current page (in order to save memory and CPU overhead). In the semi-sleep state, the situation you mentioned should appear. Condition.
You can consider trying the App version. The App version uses an independent kernel and should avoid entering a semi-sleep state.
这个应该不是代码层面的问题，而是浏览器的机制问题。据我所知，Chrome 浏览器（包括Chrome内核的所有浏览器），在离开当前页面后会进入半休眠状态（为了节约内存和cpu开销），半休眠状态下应该会出现您提到的这种情况。 您可以考虑试试 App 版本，App 版本使用的是独立内核，应该会避免进入半休眠状态
好的，谢谢大佬
Bot detected the issue body's language is not English, translate it automatically.
This should not be a code-level problem, but a browser mechanism problem. As far as I know, the Chrome browser (including all browsers with Chrome core) will enter a semi-sleep state after leaving the current page (in order to save memory and CPU overhead). In the semi-sleep state, the situation you mentioned should appear. Condition. You can consider trying the App version. The App version uses an independent kernel and should avoid entering a semi-sleep state.
Okay, thank you, boss