Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: GoCQ 意外崩溃,报错 invalid memory address or nil pointer dereference #2437

Closed
4 tasks done
lgc2333 opened this issue Sep 17, 2023 · 1 comment
Closed
4 tasks done
Labels
bug? The issue author think this is a bug

Comments

@lgc2333
Copy link

lgc2333 commented Sep 17, 2023

请确保您已阅读以上注意事项,并勾选下方的确认框。

  • 我已经仔细阅读上述教程和 "提问前需知"
  • 我已经使用 dev分支版本 测试过,问题依旧存在。
  • 我已经在 Issue Tracker 中找过我要提出的问题,没有找到相同问题的ISSUE。
  • 我已知晓并同意,此处仅用于汇报程序中存在的问题。若这个 Issue 是关于其他非程序本身问题,则我的 Issue 可能会被无条件自动关闭或/并锁定。(这些问题应当在 Discussion 板块提出。)

go-cqhttp 版本

f16d72f

运行环境

Ubuntu 23.04

运行架构

AMD64

连接方式

WebSocket (反向)

使用协议

6 | aPad(尝试过 8.9.63,更换协议至 8.9.70 依然崩溃)

重现步骤

原因未知

sign-servers 下仅填写一个签名服务器配置,之后运行 GoCQ
(我也不知道具体原因是不是这个,看到某个群友说的) 并不是

期望的结果是什么?

运行正常不崩溃

实际的结果是什么?

运行一段时间后崩溃

简单的复现代码/链接(可选)

No response

日志记录(可选)

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x974ec3]

goroutine 50 [running]:
github.com/Mrs4s/go-cqhttp/cmd/gocq.signStartRefreshToken(0x28)
    github.com/Mrs4s/go-cqhttp/cmd/gocq/qsign.go:400 +0x323
created by github.com/Mrs4s/go-cqhttp/cmd/gocq.LoginInteract
    github.com/Mrs4s/go-cqhttp/cmd/gocq/main.go:172 +0x545

补充说明(可选)

No response

@lgc2333 lgc2333 added the bug? The issue author think this is a bug label Sep 17, 2023
@lgc2333 lgc2333 changed the title [Bug]: 只填写一个 sign-server 时会出现 invalid memory address or nil pointer dereference [Bug]: GoCQ 意外崩溃,报错 invalid memory address or nil pointer dereference Sep 17, 2023
@YumeMichi
Copy link
Contributor

cmd/gocq/qsign.go 400行的cs.URL换成master.URL看看

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug? The issue author think this is a bug
Projects
None yet
Development

No branches or pull requests

3 participants