Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Cerrado
  • ¿Algo no está bien?
#66,303 2 comentarios 1 reacción 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@trivikr ya está trabajando en esto.

Desde el 25/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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

Lenguaje dominante
JavaScript
Estrellas
122k
Forks
37.4k
Merge medio
4 d 8 h
PR fusionados (30 d)
293

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de nodejs/node

Todos los issues de nodejs/node

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.