Pool not released after (a specific) Puppeteer error
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 42/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- javascript, node.js
- 领域
- backend
调研方向
从 lib/pool.js 第 356 行附近开始，issue 中指出 worker 应在 Puppeteer detached-frame error 后释放。复现或跟踪 detached-frame failure 以及随后的 pool acquisition timeout；完成标准是失败的 requests 释放其 workers，使后续的 export requests 能够获取可用条目，而无需重启服务器。
由索引模型根据 Issue 内容生成。
描述
We are running the Highcharts export server on Heroku. At some point we get some Puppeteer detached frame errors. We are not sure why, maybe because of the specific chart configs being exported (to SVG). However, those export requests crashing isn't that big of a deal, but after those errors the worker pool seems to be exhausted (old workers are not released to the pool) and all subsequent requests crash with "Error encountered when acquiring an available entry". They keep crashing until we manually restart the export server.
So in detail, we first get two of these errors (we have a minWorker pool size of 2):
Request to export server not successful. code: 400, response: {"statusCode":400,"message":"[pool] In pool.postWork: Attempted to use detached Frame 'B3381E6334D5B8B0CADB3E9197D43969'."}
After which all subsequent requests crash with:
Request to export server not successful. code: 400, response: {"statusCode":400,"message":"[pool] In pool.postWork: For request with ID e0b3bd5f9ec04233ae22320e5ab5f370 - Error encountered when acquiring an available entry: 5001.070848ms."}
Looking at the code in pool.js, the worker should be released after the first error, but for some reason it doesn't and we can't acquire any new workers afterwards. So we end up with a running export server process with no workers in the pool at all, which seems pretty useless. Only way to fix this is to (manually) restart the process.
Any help with this would be appreciated!
- 主要语言
- JavaScript
- 星标
- 368
- 派生
- 265
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
highcharts/node-export-server 的其他 Issue
-
Update Puppeteer to version 25.11.0+ to allow ARM64 linux images to run node-export-server可能已有人在做 @daniatic 于 4 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 75/100
highcharts/node-export-server#686 ·
-
难度 3/5 1-2 天 新手友好度 35/100
highcharts/node-export-server#680 · 1 条评论 ·
-
难度 5/5 一周以上 新手友好度 25/100
highcharts/node-export-server#679 ·
-
难度 3/5 1-2 天 新手友好度 45/100
highcharts/node-export-server#678 ·
-
难度 4/5 3-5 天 新手友好度 30/100
highcharts/node-export-server#676 ·
查看 highcharts/node-export-server 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
processing/p5.sound.js#123 ·
-
难度 1/5 1-3 小时 新手友好度 82/100
PhilflowIO/dav-mcp#146 ·
维护者通常 1 天内回复
-
good first issue hacktoberfest
难度 2/5 1-3 小时 新手友好度 82/100
Tanishq964/trail-kit.#4 ·
-
new icon permissions in review
难度 2/5 1-3 小时 新手友好度 62/100
simple-icons/simple-icons#15067 ·
维护者通常 1 天内回复
-
status: needs triage
难度 2/5 1-3 小时 新手友好度 62/100
mastra-ai/mastra#26562 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复