Desktop profile-backend pool CPU and spawn fixes
Cluster 102978. Data as of
Nothing open on GitHub. Fix merged in #108134 on 11 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #108134. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #108134. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a desktop bug where the profile-backend pool fails to drain properly, causing excessive backend processes, high CPU usage, and app self-restarts. Fixes target unnecessary backend spawning on launch, roster ticks, and bot tile cold-starts.
Open issues0
Open PRs0
Fixes on record
-
#107969 Desktop: open bot tiles no longer cold-start or pin pooled backends from the background (#103375, salvage #103399)
files:
apps/desktop/electron/main.ts,apps/desktop/electron/registry-primary-profile-scope.test.ts,apps/desktop/src/api/sessions.ts,apps/desktop/src/app/contrib/hooks/use-background-sync.test.ts,apps/desktop/src/app/contrib/hooks/use-background-sync.ts,apps/desktop/src/global.d.ts,apps/desktop/src/store/gateway-connection-lifecycle.test.ts,apps/desktop/src/store/gateway.ts -
#108134 Desktop: Bot Mode no longer spawns or dials a backend per profile on launch and every roster tick (#102978, #99336, #102913)
files:
apps/desktop/src/plugins/hermes-bots/profile-ops.test.ts,apps/desktop/src/plugins/hermes-bots/profile-ops.ts
1 PR closed without merging
From the close comments: done elsewhere 1
-
#103522 fix: [Desktop] Profile-backend pool never drains: 3 slots vs ~60 profiles, long-lived serve/backend processes climb to ~99% CPU, app self-restarts (#102978) · done elsewhere →
52fb4e0,#107969,#102978,#108134
Closed issues · 1
- Closed#102978[Desktop] Profile-backend pool never drains: 3 slots vs ~60 profiles, long-lived serve/backend processes climb to ~99% CPU, app self-restarts
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab