Skip to content

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

Closed
#66304
Closed
node --report-on-process-timeout writes truncated report when a Worker is blocked#66303
#66304
Assignees
trivikr
Labels
reportIssues and PRs related to Node.js diagnostic reports.

Description

@trivikr
trivikr
opened on Sep 25, 2026

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

Activity

  1. trivikr
    self-assigned this
    on Sep 25, 2026
  2. trivikr
    added
    reportIssues and PRs related to Node.js diagnostic reports.
    on Sep 25, 2026
  3. trivikr
    changed the title [-]--report-on-process-timeout writes truncated report when a Worker is blocked[/-] [+]node --report-on-process-timeout writes truncated report when a Worker is blocked[/+] on Sep 25, 2026

  4. jasnell commented on Sep 25, 2026

    @jasnell
    jasnell
    on Sep 25, 2026
    Member

    @trivikr ... i'm going to assume since you assigned this to yourself you're going to take a stab at fixing... I did a quick check and this is what I found:

    The bug is in node_report.cc, not the watchdog. The report waits with no time limit for every Worker to respond to its interrupt. A Worker blocked in a native synchronous call never responds. Any main-thread report hangs forever in this case; --process-timeout just turns the hang into a truncated file. Specifically, node_report.cc hands and the process timeout grace period cuts it off.

  5. trivikr commented on Sep 25, 2026

    @trivikr
    trivikr
    on Sep 25, 2026
    MemberAuthor

    Yes. A proposed a 2-second time limit for worker threads in #66304

  6. nodejs-github-bot
    closed this as completedin #66304on Sep 27, 2026
  7. nodejs-github-bot
    added a commit that references this issue on Sep 27, 2026

    report: skip unresponsive workers on process timeout

    75e4bbe
  8. HoonDongKang
    added a commit that references this issue on Sep 28, 2026

    report: skip unresponsive workers on process timeout

    a06b41d
  9. aduh95
    added 2 commits that reference this issue on Sep 28, 2026

    report: skip unresponsive workers on process timeout

    10f3088

    report: skip unresponsive workers on process timeout

    52bbf8c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

reportIssues and PRs related to Node.js diagnostic reports.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions