René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"node --report-on-process-timeout writes truncated report when a Worker is blocked","articleBody":"### Version\n\nmain\n\n### Platform\n\n```text\nAll\n```\n\n### Subsystem\n\nreport\n\n### What steps will reproduce the bug?\n\n```js\nimport { Worker } from 'node:worker_threads';\n\nnew Worker(`require('node:child_process').execFileSync('sleep', ['30']);`, { eval: true });\n```\n\nRun with\n```console\n$ node --process-timeout=1s --report-on-process-timeout repro.js\n```\n\n### How often does it reproduce? Is there a required condition?\n\nAlways\n\n### What is the expected behavior? Why is that the expected behavior?\n\nA 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.\n\n\n### What do you see instead?\n\n```console\n(node:2291000) Process timed out after 1s (--process-timeout). Exiting with code 124.\nMain thread was not executing JavaScript.\nResources keeping the event loop alive:\n    Worker (thread 1, name 'WorkerThread')\n\nWriting 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.\n```\n\n```console\n$ node -e \"JSON.parse(require('fs').readFileSync('report.20260925.212601.2291000.0.001.json'))\"\nSyntaxError: Expected property name or '}' in JSON at position 8192 (line 338 column 9)\n```\n\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/trivikr","@type":"Person","name":"trivikr"},"datePublished":"2026-09-25T21:33:21Z","url":"https://github.com/nodejs/node/issues/66303"}