{"version":"2.1.311","anchor":"event-loop-stall-detector-accounts-for-timer-slack","canonical_anchor":"event-loop-stall-detector-accounts-for-timer-slack","heading":"Fewer false reports of Claude Code freezing","tier":"notice","area":"Performance","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/event-loop-stall-detector-accounts-for-timer-slack","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Fewer false reports of Claude Code freezing\n\nThe freeze detector now allows for the system's timer slack, so small delays it causes are no longer reported as freezes\n\n**What**\n\nClaude Code watches for moments when it stops responding for a short time, called stalls. It now takes timer slack into account. Timer slack is a small delay the operating system may add to timers to save power. On Linux it reads this from `\/proc\/self\/timerslack_ns`. It also measures processor time between checks.\n\n- Late checks that fall within the timer slack are counted separately and are no longer reported as stalls.\n\n- Stall reports now include the timer slack and the count of late checks within it.\n\n- If the slack cannot be read, stalls are reported without allowing for it.\n\n- After the computer has probably been asleep, Claude Code now resets its terminal settings even when no stall was found.\n\n**Why**\n\nIt means fewer stall reports that were really just the system's normal timer delay.\n\n- Area: Performance\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}