Aggressive Process Termination Causes Race Conditions

[akramcodez]

Description

The service enforces a hard timeout when terminating processes. If a process does not exit within 200ms after receiving SIGTERM, it is forcefully killed with SIGKILL:

const SIGKILL_TIMEOUT_MS = 200;
// ...
process.kill(-child.pid, 'SIGTERM');
await new Promise((res) => setTimeout(res, SIGKILL_TIMEOUT_MS));
if (!exited) {
  process.kill(-child.pid, 'SIGKILL');
}

This timeout is extremely short for many real-world applications.

Impact

• Risk of data corruption for processes performing I/O or cleanup
• Possible leftover lockfiles (e.g., git, npm) and inconsistent on-disk state
• Reduced stability when terminating long-running or heavy processes

[tikendrasahu-ux]

const SIGKILL_TIMEOUT_MS = 200;
// ...
process.kill(-child.pid, 'SIGTERM');
await new Promise((res) => setTimeout(res, SIGKILL_TIMEOUT_MS));
if (!exited) {
process.kill(-child.pid, 'SIGKILL');
}