{"version":"2.1.239","anchor":"stall-detection-separates-real-hangs-from-clock-jumps","canonical_anchor":"stall-detection-separates-real-hangs-from-clock-jumps","heading":"Stall detection separates real hangs from clock jumps","tier":"notice","area":"Diagnostics","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/stall-detection-separates-real-hangs-from-clock-jumps","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Stall detection separates real hangs from clock jumps\n\nA system clock jump no longer gets misreported as Claude Code hanging.\n\n**What**\n\nThe event-loop stall detector now measures elapsed time with a monotonic clock as well as the wall clock, so a system clock jump is no longer reported as a stall.\n\n**Details**\n\n- New reported fields: monotonic stall duration, clock jump, whether a slow terminal write was blocking, and whether a resume signal (SIGCONT) was seen, meaning the machine had been suspended.\n- Reporting is deferred to the next tick so measuring the stall does not lengthen it.\n- Runs whenever the detector is started.\n\n**Evidence**\n\n`monotonic_stall_ms`\n\n- Area: Diagnostics\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}