wip(native): capture WER custom metadata

[jpnurmi]

App:

WerRegisterCustomMetadata(L"foo", L"ooo");
WerRegisterCustomMetadata(L"bar", L"aaa");
WerRegisterCustomMetadata(L"baz", L"zzz");

Context:

{
  "contexts": {
    "wer": {
      "type": "wer",
      "report_id": "...",
      "metadata": {
        "foo": "ooo",
        "bar": "aaa",
        "baz": "zzz"
      }
    }
  }
}

Sentry:

[linear-code]

TGDX-58

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d5dc747. Configure here.}

[cursor]

WER module no longer waits for daemon minidump capture

Medium Severity

The WER out-of-process module previously waited for the crash daemon to finish processing (including minidump capture via ReadProcessMemory/MiniDumpWriteDump) and then explicitly called TerminateProcess. That wait loop and TerminateProcess are now removed, so process_wer_exception signals the daemon and returns immediately. Meanwhile, the crash handler in the app process returns EXCEPTION_CONTINUE_SEARCH unconditionally (when WER is enabled), relying entirely on the WER module to notify the daemon. Without the wait, WER can proceed through its callback sequence, finish its report, and terminate the crashed process before the daemon completes minidump capture — resulting in an incomplete or failed minidump.

Additional Locations (1)

• src/backends/native/sentry_crash_handler.c#L943-L950

 

^{Reviewed by Cursor Bugbot for commit d5dc747. Configure here.}