Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

node --report-on-process-timeout writes truncated report when a Worker is blocked

已关闭
#66,303 2 条评论 1 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@trivikr 已经在做这个了。

开始于 2026年9月25日。

评估

这个 Issue 还没有评估数据。

描述

report
Version

main

Platform
All
Subsystem

report

What steps will reproduce the bug?
import { Worker } from 'node:worker_threads';

new Worker(`require('node:child_process').execFileSync('sleep', ['30']);`, { eval: true });

Run with

$ node --process-timeout=1s --report-on-process-timeout repro.js
How often does it reproduce? Is there a required condition?

Always

What is the expected behavior? Why is that the expected behavior?

A complete, valid JSON report is written. Blocked Workers could be left out or marked as unresponsive. A stuck Worker is exactly the case where you'd want the report. The forced-exit message should also start on its own line.

What do you see instead?
(node:2291000) Process timed out after 1s (--process-timeout). Exiting with code 124.
Main thread was not executing JavaScript.
Resources keeping the event loop alive:
    Worker (thread 1, name 'WorkerThread')

Writing Node.js report to file: report.20260925.212601.2291000.0.001.json(node:2291000) The process did not finish exiting within 5000ms after --process-timeout expired. Forcing exit.
$ node -e "JSON.parse(require('fs').readFileSync('report.20260925.212601.2291000.0.001.json'))"
SyntaxError: Expected property name or '}' in JSON at position 8192 (line 338 column 9)
Additional information

No response

主要语言
JavaScript
星标
122k
派生
37.4k
平均合并
4 天 12 小时
30 天内合并 PR
296

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nodejs/node 的其他 Issue

查看 nodejs/node 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。