Skip to content

[BUG] QQ账号异常导致幽灵进程和内存占用异常 #792

Description

@XXY233

系统版本

Debian 13.5

QQNT 版本

3.2.20-40768

LLBot 版本

7.12.14

OneBot 客户端

No response

发生了什么?

登录的QQ号异常(例如手机尝试登录该QQ,然后没登录成功,造成账号状态异常;或者腾讯冻结该QQ号)时,后台进程不会结束并占用大量内存。

如何复现

  1. 使用命令./start.sh运行LLBot
  2. 使这个QQ账号状态异常
  3. 运行start.sh的脚本已经退出了,最后的提示:
    2026-06-24 21:36:12 [I] onebot11-adapter WebSocket 事件上报 ws://127.0.0.1:7070/onebot/v11/ meta_event
    2026-06-24 21:37:12 [I] onebot11-adapter WebSocket 事件上报 ws://127.0.0.1:7070/onebot/v11/ meta_event
    2026-06-24 21:38:12 [I] onebot11-adapter WebSocket 事件上报 ws://127.0.0.1:7070/onebot/v11/ meta_event
    [PMHQ-INIT] Step 0: Checking main process
    [PMHQ-INIT] Step 0: Not main process (PID 4079092), skipping. cmdline: /opt/QQ/qq --type=relauncher --no-sandbox --- /opt/QQ/qq --relaunch --no-sandbox --disable-gpu
    2026-06-24 21:38:51 [E] pmhq PMHQ WebSocket 连接错误,可能 QQ 未启动,正在等待 QQ 启动进行重连...
    2026-06-24 21:38:52 [I] pmhq PMHQ WebSocket 连接成功
    QQ 进程退出,状态: exit status: 0
    延迟 15 秒后退出...
    将在 15 秒后终止子进程...
    2026-06-24 21:39:12 [I] onebot11-adapter WebSocket 事件上报 ws://127.0.0.1:7070/onebot/v11/ meta_event
    正在终止子进程...
    正在终止 QQ 进程...
    
  4. LLBot的日志开始一直刷 "app Error: write EPIPE"
    2026-06-24 21:38:51 [E] pmhq PMHQ WebSocket 连接错误,可能 QQ 未启动,正在等待 QQ 启动进行重连...
    2026-06-24 21:38:52 [I] pmhq PMHQ WebSocket 连接成功
    2026-06-24 21:39:12 [I] onebot11-adapter WebSocket 事件上报 ws://127.0.0.1:7070/onebot/v11/ meta_event
    2026-06-24 21:39:23 [E] pmhq PMHQ WebSocket 连接错误,可能 QQ 未启动,正在等待 QQ 启动进行重连...
    2026-06-24 21:39:32 [W] pmhq [PMHQ] Triggering disconnect callback, duration: 10000ms, timeout: 10000ms
    2026-06-24 21:39:32 [W] email-notification-service [EmailNotification] PMHQ disconnected for 10000ms
    2026-06-24 21:39:32 [I] email-notification-service [EmailNotification] Bot went offline, sending notification
    2026-06-24 21:39:32 [E] app Error: write EPIPE
                                at afterWriteDispatched (node:internal/stream_base_commons:159:15)
                                at writeGeneric (node:internal/stream_base_commons:150:3)
                                at Socket._writeGeneric (node:net:966:11)
                                at Socket._write (node:net:978:8)
                                at writeOrBuffer (node:internal/streams/writable:570:12)
                                at _write (node:internal/streams/writable:499:10)
                                at Writable.write (node:internal/streams/writable:508:10)
                                at console.value (node:internal/console/constructor:313:16)
                                at console.log (node:internal/console/constructor:416:26)
                                at Console.export (file:///home/xxxxx/bot/llone/bin/llbot/node_modules/reggol/lib/node.js:215:15)
    2026-06-24 21:39:32 [E] app Error: write EPIPE
                                at afterWriteDispatched (node:internal/stream_base_commons:159:15)
                                at writeGeneric (node:internal/stream_base_commons:150:3)
                                at Socket._writeGeneric (node:net:966:11)
                                at Socket._write (node:net:978:8)
                                at writeOrBuffer (node:internal/streams/writable:570:12)
                                at _write (node:internal/streams/writable:499:10)
                                at Writable.write (node:internal/streams/writable:508:10)
                                at console.value (node:internal/console/constructor:313:16)
                                at console.log (node:internal/console/constructor:416:26)
                                at Console.export (file:///home/xxxxx/bot/llone/bin/llbot/node_modules/reggol/lib/node.js:215:15)
    
    Image
  5. 但是LLBot的进程仍然在后台运行,并占用大量内存(原先只占用100多M,现已飙升至4000多M)
    Image

期望的结果?

LLBot应该正常结束后台进程,并不要占用这么多内存。

LLBot 运行日志

OneBot 客户端运行日志

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions