{"version":"2.1.269","anchor":"remote-settings-service-now-tracks-process-exit-and-stops-pe","canonical_anchor":"remote-settings-service-now-tracks-process-exit-and-stops-pe","heading":"Remote settings clients now stop refreshing after the process exits","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/remote-settings-service-now-tracks-process-exit-and-stops-pe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Remote settings clients now stop refreshing after the process exits\n\nThe remote settings and GrowthBook clients now detect process exit and stop their periodic background refresh\n\n**What**\n\n- The remote settings\/eval class now tracks `processExitListenerInstalled` and `processExited` flags, along with an `onProcessExit` handler that marks itself as exited and stops its periodic refresh. A related class also gained a `backstopReleased` flag, set when a load-promise safety timeout expires and resolves anyway.\n\n- The GrowthBook client's `createClient()` now installs a one-time process `exit` listener, and its `startPeriodicRefresh()` now checks the new `processExited` flag before starting any refresh loop.\n\n**Why**\n\nThis stops these clients from trying to do background refresh work after the process has already exited, avoiding wasted work or errors during shutdown.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}