-
Notifications
You must be signed in to change notification settings - Fork 28.8k
New issue
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
Enable Electron Crash reporter for all processes after Electron update #21944
Labels
electron
Issues and items related to Electron
engineering
VS Code - Build / issue tracking / etc.
feature-request
Request for new features or functionality
upstream
Issue identified as 'upstream' component related (exists outside of VS Code)
Milestone
Comments
ramya-rao-a
added
feature-request
Request for new features or functionality
electron-update
labels
Apr 10, 2017
For the May milestone, we have enabled the crash reporter in the child process that starts the extension host. |
And only on macOS. |
@ramya-rao-a fyi I am not convinced this actually works, so far I did not find a crash from the extension host on HockeyApp. Maybe you could also have a look. |
bpasero
added
workbench
upstream
Issue identified as 'upstream' component related (exists outside of VS Code)
and removed
electron-update
labels
Nov 11, 2017
Closing this in favor of #36540. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
electron
Issues and items related to Electron
engineering
VS Code - Build / issue tracking / etc.
feature-request
Request for new features or functionality
upstream
Issue identified as 'upstream' component related (exists outside of VS Code)
Once a newer version (>= 1.5.1)of electron is adopted, all node processes spawned in VS Code need to initialize the crash reporter
https://github.com/electron/electron/blob/master/docs/api/crash-reporter.md#methods
The text was updated successfully, but these errors were encountered: