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

Add killed argument for webContents.on("crashed") and app.on("gpu-process-crashed") events #7241

Merged
merged 1 commit into from Sep 19, 2016

Conversation

Projects
None yet
2 participants
@miniak
Contributor

miniak commented Sep 18, 2016

This indicates whether the renderer or gpu process was killed intentionally. Chrome's sad tab also distinguishes between crashed and killed tabs.

@miniak miniak changed the title from Add killed argument for webContents.on("crashed") and app.on("gpu-pro…cess-crashed") events to Add killed argument for webContents.on("crashed") and app.on("gpu-process-crashed") events Sep 18, 2016

@zcbenz

This comment has been minimized.

Contributor

zcbenz commented Sep 19, 2016

👍

@zcbenz zcbenz merged commit 26004f1 into electron:master Sep 19, 2016

1 of 2 checks passed

continuous-integration/appveyor/pr AppVeyor build failed
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details

@miniak miniak deleted the miniak:crashed-killed branch Sep 19, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment