Bug type
Crash (process/app exits or hangs)
Summary
Clicking the session dropdown menu in Control UI and switching from "main" to "qqbot" causes the frontend to freeze with high CPU usage (fans spinning loudly). No console errors are logged.
Steps to reproduce
Open Control UI at http://127.0.0.1:18789/
Click the session dropdown menu (top-left corner)
Switch from "main heartbeat" to "qqbot" session
Frontend freezes, becomes unresponsive to any clicks
Computer fans start spinning loudly (high CPU usage)
Expected behavior
Session should switch smoothly without freezing.
Actual behavior
Frontend becomes completely unresponsive
CPU usage spikes (fans spinning loudly)
No JavaScript errors in browser console
Gateway backend remains healthy (logs show no errors)
Browser tab needs to be force-closed or refreshed
OpenClaw version
2026.3.13
Operating system
Windows11
Install method
npm global
Model
glm-5
Provider / routing chain
I don't understand this question
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Gateway logs show normal WebSocket disconnect/reconnect when attempting the switch:
webchat disconnected code=1001 reason=n/a
webchat connected conn=xxx
No error messages in backend.
Impact and severity
Affected: qqbot users on 2026.3.13
Severity: High (I can't use qqbot)
Frequency: 6/6 observed attempts
Consequence: I can't use qqbot, and high CPU for the tab process
Additional information
Environment:
OpenClaw Version: 2026.3.13 (61d171a)
OS: WSL2 on Windows 10 (Linux 6.6.87.2-microsoft-standard-WSL2)
Node: v22.22.1
Browser: Microsoft Edge 146.0.0.0 (Windows 10)
Channels: QQBot + Feishu (both enabled)
Active Sessions
agent:main:main (direct, webchat)
agent:main:qqbot:direct:23b070a… (direct, qqbot)
agent:main:feishu:group:oc_5d3b… (group, feishu)
agent:main:feishu:direct:ou_fd2… (direct, feishu)
Possible Cause
Frontend likely enters an infinite render loop or state update cycle when loading sessions from certain channels (possibly QQBot-specific).
Workaround
Force refresh: Ctrl + Shift + R
Avoid using dropdown menu for session switching
Additional Context
Issue occurs consistently, 100% reproducible
Browser DevTools Console shows no errors
Browser Task Manager shows high CPU for the tab process
Bug type
Crash (process/app exits or hangs)
Summary
Clicking the session dropdown menu in Control UI and switching from "main" to "qqbot" causes the frontend to freeze with high CPU usage (fans spinning loudly). No console errors are logged.
Steps to reproduce
Open Control UI at http://127.0.0.1:18789/
Click the session dropdown menu (top-left corner)
Switch from "main heartbeat" to "qqbot" session
Frontend freezes, becomes unresponsive to any clicks
Computer fans start spinning loudly (high CPU usage)
Expected behavior
Session should switch smoothly without freezing.
Actual behavior
Frontend becomes completely unresponsive
CPU usage spikes (fans spinning loudly)
No JavaScript errors in browser console
Gateway backend remains healthy (logs show no errors)
Browser tab needs to be force-closed or refreshed
OpenClaw version
2026.3.13
Operating system
Windows11
Install method
npm global
Model
glm-5
Provider / routing chain
I don't understand this question
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Gateway logs show normal WebSocket disconnect/reconnect when attempting the switch: webchat disconnected code=1001 reason=n/a webchat connected conn=xxx No error messages in backend.Impact and severity
Affected: qqbot users on 2026.3.13
Severity: High (I can't use qqbot)
Frequency: 6/6 observed attempts
Consequence: I can't use qqbot, and high CPU for the tab process
Additional information
Environment:
OpenClaw Version: 2026.3.13 (61d171a)
OS: WSL2 on Windows 10 (Linux 6.6.87.2-microsoft-standard-WSL2)
Node: v22.22.1
Browser: Microsoft Edge 146.0.0.0 (Windows 10)
Channels: QQBot + Feishu (both enabled)
Active Sessions
agent:main:main (direct, webchat)
agent:main:qqbot:direct:23b070a… (direct, qqbot)
agent:main:feishu:group:oc_5d3b… (group, feishu)
agent:main:feishu:direct:ou_fd2… (direct, feishu)
Possible Cause
Frontend likely enters an infinite render loop or state update cycle when loading sessions from certain channels (possibly QQBot-specific).
Workaround
Force refresh: Ctrl + Shift + R
Avoid using dropdown menu for session switching
Additional Context
Issue occurs consistently, 100% reproducible
Browser DevTools Console shows no errors
Browser Task Manager shows high CPU for the tab process