We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
在重新恢复下载时会导致Gopeed闪退:我使用了百度网盘插件通过Cookies下载文件,在锁屏+重新联网的情况下会出现恢复下载就导致Gopeed出现闪退。
感觉触发条件和 #529 有点相似,但应该是HTTP类型的下载?
在1.5.5及1.6.3下均会出现
Windows 10 22H2(Build 19045.5131)
panic: interface conversion: interface {} is map[string]interface {}, not *http.ReqExtra goroutine 899 [running]: github.com/GopeedLab/gopeed/internal/protocol/http.(*Fetcher).buildRequest(0xc000199860, {0x7ffd46575590, 0xc000e9ceb0}, 0xc00019cb80) D:/a/gopeed/gopeed/internal/protocol/http/fetcher.go:391 +0x51c github.com/GopeedLab/gopeed/internal/protocol/http.(*Fetcher).fetchChunk(0xc000199860, 0x7ffd45456a93?, {0x7ffd46575590, 0xc000e9ceb0}) D:/a/gopeed/gopeed/internal/protocol/http/fetcher.go:313 +0x145 github.com/GopeedLab/gopeed/internal/protocol/http.(*Fetcher).fetch.func1() D:/a/gopeed/gopeed/internal/protocol/http/fetcher.go:257 +0x26 golang.org/x/sync/errgroup.(*Group).Go.func1() C:/Users/runneradmin/go/pkg/mod/golang.org/x/[email protected]/errgroup/errgroup.go:78 +0x50 created by golang.org/x/sync/errgroup.(*Group).Go in goroutine 889 C:/Users/runneradmin/go/pkg/mod/golang.org/x/[email protected]/errgroup/errgroup.go:75 +0x96 panic: interface conversion: interface {} is map[string]interface {}, not *http.ReqExtra
The text was updated successfully, but these errors were encountered:
感谢反馈 我看看
Sorry, something went wrong.
你是手点继续下载然后闪退吗,还是扩展触发的
手动点击的
1.6.4已经修复了.
No branches or pull requests
Description(required)
在重新恢复下载时会导致Gopeed闪退:我使用了百度网盘插件通过Cookies下载文件,在锁屏+重新联网的情况下会出现恢复下载就导致Gopeed出现闪退。
感觉触发条件和 #529 有点相似,但应该是HTTP类型的下载?
App Version(required)
在1.5.5及1.6.3下均会出现
OS Version(required)
Windows 10 22H2(Build 19045.5131)
Log
The text was updated successfully, but these errors were encountered: