openclaw - 💡(How to fix) Fix Discord voice enabled causes sustained gateway CPU spin after embedded Discord connects [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#73753Fetched 2026-04-29 06:15:34
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
commented ×1mentioned ×1subscribed ×1

When channels.discord.voice.enabled=true (the default), the embedded Discord provider causes openclaw-gateway to sustain ~100% CPU on Linux after bot accounts connect. This is a separate issue from #73709 (which covers the intent-selection bug when voice is disabled) — this is the underlying voice runtime CPU problem that remains even after the GuildVoiceStates intent fix.

Root Cause

  • OpenClaw 2026.4.26, embedded Discord with voice enabled → gateway sustains ~100% CPU on Linux (Hetzner CPX31, 4 vCPU AMD) after bot accounts connect
  • Setting channels.discord.voice.enabled=false alone was insufficient — CPU spin persisted
  • Removing GuildVoiceStates from gateway intents (via local patch to resolveDiscordGatewayIntents()) caused CPU to settle after startup
  • All six embedded Discord text bot accounts connect and operate normally with voice disabled
  • Conclusion: the voice/voice-state path is strongly implicated in the CPU spin, but the deeper voice runtime root cause (voice-state event handling, voice connection lifecycle, or VoicePlugin initialization) has not been fully isolated

Fix Action

Fix / Workaround

  • OpenClaw 2026.4.26, embedded Discord with voice enabled → gateway sustains ~100% CPU on Linux (Hetzner CPX31, 4 vCPU AMD) after bot accounts connect

  • Setting channels.discord.voice.enabled=false alone was insufficient — CPU spin persisted

  • Removing GuildVoiceStates from gateway intents (via local patch to resolveDiscordGatewayIntents()) caused CPU to settle after startup

  • All six embedded Discord text bot accounts connect and operate normally with voice disabled

  • Conclusion: the voice/voice-state path is strongly implicated in the CPU spin, but the deeper voice runtime root cause (voice-state event handling, voice connection lifecycle, or VoicePlugin initialization) has not been fully isolated

  • With voice enabled: gateway unusable at idle on modest Linux hardware (~100% CPU, gateway RPC timeouts)

  • With voice disabled + #73709 local patch: gateway stable at ~0-1% CPU idle, all text bots functional

  • Discord voice feature effectively unusable on the current release

RAW_BUFFERClick to expand / collapse

Bug Report

Summary

When channels.discord.voice.enabled=true (the default), the embedded Discord provider causes openclaw-gateway to sustain ~100% CPU on Linux after bot accounts connect. This is a separate issue from #73709 (which covers the intent-selection bug when voice is disabled) — this is the underlying voice runtime CPU problem that remains even after the GuildVoiceStates intent fix.

Version

OpenClaw v2026.4.26

Relationship to #73709

  • #73709channels.discord.voice.enabled=false still requests GuildVoiceStates (intent-selection bug)
  • This issuechannels.discord.voice.enabled=true (default) causes gateway CPU spin; the voice runtime path itself appears to be the source

Evidence

  • OpenClaw 2026.4.26, embedded Discord with voice enabled → gateway sustains ~100% CPU on Linux (Hetzner CPX31, 4 vCPU AMD) after bot accounts connect
  • Setting channels.discord.voice.enabled=false alone was insufficient — CPU spin persisted
  • Removing GuildVoiceStates from gateway intents (via local patch to resolveDiscordGatewayIntents()) caused CPU to settle after startup
  • All six embedded Discord text bot accounts connect and operate normally with voice disabled
  • Conclusion: the voice/voice-state path is strongly implicated in the CPU spin, but the deeper voice runtime root cause (voice-state event handling, voice connection lifecycle, or VoicePlugin initialization) has not been fully isolated

Impact

  • With voice enabled: gateway unusable at idle on modest Linux hardware (~100% CPU, gateway RPC timeouts)
  • With voice disabled + #73709 local patch: gateway stable at ~0-1% CPU idle, all text bots functional
  • Discord voice feature effectively unusable on the current release

Environment

  • Linux: Hetzner CPX31, 4 vCPU AMD, 8 GB RAM — ~100% CPU at idle with voice enabled
  • macOS: Apple Silicon Mac Studio — ~20-33% CPU at idle with voice enabled (less severe but present)

Related

  • #73709 — GuildVoiceStates still requested when voice disabled (prerequisite/related fix)
  • #28587 — eager channel SDK loading CPU pressure (distinct, closed)

extent analysis

TL;DR

Disabling the Discord voice feature by setting channels.discord.voice.enabled=false may mitigate the CPU spin issue, but a deeper investigation into the voice runtime is needed to fully resolve the problem.

Guidance

  • Investigate the voice-state event handling, voice connection lifecycle, or VoicePlugin initialization as potential root causes of the CPU spin.
  • Verify that removing GuildVoiceStates from gateway intents resolves the CPU issue, as it did in the local patch test.
  • Test the gateway with voice enabled on different hardware configurations to determine if the issue is specific to certain environments.
  • Consider applying the local patch to resolveDiscordGatewayIntents() as a temporary workaround to stabilize the gateway.

Example

No code snippet is provided, as the issue requires further investigation into the voice runtime.

Notes

The issue appears to be specific to the embedded Discord provider with voice enabled, and the root cause has not been fully isolated. The provided information suggests that the voice/voice-state path is implicated in the CPU spin, but further investigation is needed to determine the exact cause.

Recommendation

Apply the workaround by setting channels.discord.voice.enabled=false until a deeper investigation into the voice runtime can be conducted to fully resolve the issue. This will at least stabilize the gateway and allow for further testing and debugging.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Discord voice enabled causes sustained gateway CPU spin after embedded Discord connects [1 comments, 2 participants]