Native Crash Issues
Robo edited this page Feb 23, 2021
·
21 revisions
Pages 75
Project Management
- Roadmap
- Iteration Plans
- Development Process
- Issue Tracking
- Build Champion
- Release Process
- Running the Endgame
- Related Projects
Contributing
- How to Contribute
- Submitting Bugs and Suggestions
- Feedback Channels
- Source Code Organization
- Coding Guidelines
- Smoke Test
- Dealing with Test Flakiness
- Contributor License Agreement
- Extension API Guidelines
Documentation
Clone this wiki locally
Creating and symbolicating local crash reports
VSCode since version 1.46 now supports a new --crash-reporter-directory <absolute-path> option that you can use to produce crash dumps into that folder. Please try this option first:
- close all instances of VSCode
- run
code --crash-reporter-directory <absolute-path>from the command line- note: use
code-insidersfor the insiders version if you are using it
- note: use
- take the steps that lead to the crash
- check for a
*.dmpfile in that folder - send the
*.dmpfile back to us (email, or attach to issue)
If you can reproduce the issue running out of sources:
- Follow the instructions at https://github.com/nornagon/electron-minidump/blob/master/README.md
- Check for the symbolicated trace