[Bug] 进程偶发崩溃退出,退出码 0xC000041D,且不产生任何日志(2.0.0-beta.4 / Windows)

Open
#1,667 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
dart, flutter

Research direction

Start by tracing Windows window and tray callback handling, including how Flutter exceptions are captured and logged; the report identifies flutter_windows.dll and a possible TaskbarCreated callback but does not name source files or tests. Reproduce the intermittent 0xC000041D exit and inspect the callback and crash logging paths. Done means the crash is prevented or useful diagnostic output is produced when it occurs.

Written by the indexing model from the issue text.

Description

环境
项 值
Gopeed 2.0.0-beta.4(Windows amd64,官方 exe 安装包)
系统 Windows 11 专业版 Build 26300,AMD64
扩展 monkeyWie/bilibili v2.1.0
现象

运行过程中进程偶发自行消失,界面上无任何提示。今天共发生 4 次(含 1 次 v1.9.3 时期),其中一次成功捕获到退出码:

退出码: -1073740771 (0xC000041D)  STATUS_FATAL_USER_CALLBACK_EXCEPTION
退出时间: 2026-11-11 17:25:20
运行时长: 3 小时 14 分
关键问题:崩溃不产生任何诊断信息
  • %LOCALAPPDATA%\CrashDumps 无转储
  • WER ReportArchive / ReportQueue 无新报告
  • 应用程序事件日志无 Application Error / Windows Error Reporting 记录
  • storage/logs/crash.log、core.log、extension.log 均为 0 字节

也就是说用户端完全无法自查,只能看到一个进程凭空消失。

可能相关的系统事件

本次崩溃前 95 秒内 explorer.exe 连续崩溃并重启两次:

时间 事件
17:21:49 Winlogon 1002:外壳程序意外停止,userinit.exe 被重新启动
17:23:45 同上
17:25:20 Gopeed 崩溃(0xC000041D)

explorer 重启会向所有顶层窗口广播 TaskbarCreated,托盘程序需重新注册图标。Gopeed 常驻托盘,怀疑托盘回调在此消息中抛异常。但这只能解释其中一次(其余 3 次退出附近无 explorer 事件),因此可能还存在其他触发源,例如窗口消息处理或插件回调。

旁证

2026-11-11 12:50 的 v1.9.3 崩溃,WER 记录为:

出错模块: flutter_windows.dll
异常代码: 0xc000041d

异常类型完全相同,说明问题位于 Flutter 的 Windows 窗口/回调层,跨版本存在,非 v2 新增。

期望
  1. 修复崩溃本身
  2. 至少让崩溃留下日志或转储,便于用户反馈时提供有效信息
补充

内存问题另见 #1666,两者独立。

Dominant language
Dart
Stars
27.7k
Forks
1.8k
Avg merge
3d 3h
Merged PRs (30d)
26

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GopeedLab/gopeed

All issues in GopeedLab/gopeed

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.