microsoft / microsoft/vscode-cpptools

Investigate use of the crash reporting system in Electron/VSCode

Open
#7,356 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

internal Language Service
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Some information about how to use the crash reporting system in Electron, is here: https://github.com/microsoft/vscode/issues/118767#issuecomment-809537326

Child process are now monitored by the crash handler from runtime, you can obtain the reports following the steps https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-and-symbolicating-local-crash-reports. Once the app is quit, the crash report will be under /pending. To symbolicate, you can use https://github.com/nornagon/electron-minidump/blob/master/README.md and the symbols need to generated in the following format https://github.com/google/breakpad/blob/master/README.ANDROID#L93-L113. I will update the documentation on this in the wiki.

Opening this issue to track trying to make use of this system for collecting crash diagnostics. This would be an improvement over our current system, which currently only receives crash stacks from macOS.

Contributor guide

Open the contributing guide

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.

Research direction

Start with the linked VS Code crash-reporting guidance, the crash-reporter-directory/pending location, and the electron-minidump and Breakpad symbol-format documentation. Determine whether this project can collect and symbolicate diagnostics beyond macOS, then document or implement a concrete integration path and its completion criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron
Domain
desktop, observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.