{"version":"2.1.288","anchor":"event-loop-stall-detector-told-to-attribute-sigcont-in-non-p","canonical_anchor":"event-loop-stall-detector-told-to-attribute-sigcont-in-non-p","heading":"Stall tracking accounts for resuming a suspended Claude Code","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/event-loop-stall-detector-told-to-attribute-sigcont-in-non-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Stall tracking accounts for resuming a suspended Claude Code\n\nIn interactive sessions, the detector for program stalls is told to take a resume after suspension into account\n\n**Unclear.** It is not confirmed what accounting for SIGCONT does inside the detector.\n\n**What**\n\nClaude Code watches for moments when it freezes up, called event-loop stalls (the event loop is the part of the program that handles work in turn). In interactive sessions, though not in print mode, this detector is now told to account for SIGCONT, the signal a program gets when it resumes after being suspended, for example after Ctrl+Z.\n\nThis sits behind `tengu_drift_lantern`. The flag server returned it as on for this site's account and for the anonymous baseline, in readings not taken under this release.\n\n**Why**\n\nThis is about the accuracy of stall measurements Claude Code collects. It changes the data rather than how Claude Code behaves for you. It appears meant to stop time spent suspended from being counted as a stall.\n\n- Flag `tengu_drift_lantern`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.288; this account: on, anonymous baseline: on, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}