8000 fix: crash when calling setProgressBar on macOS by zcbenz · Pull Request #16374 · electron/electron · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix: crash when calling setProgressBar on macOS #16374

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

Merged
merged 2 commits into from
Feb 4, 2019

Conversation

zcbenz
Copy link
Contributor
@zcbenz zcbenz commented Jan 12, 2019

Description of Change

Depending on the version of macOS and macOS SDK, the system may install a default contentView for the dock, resulting in crashes like #14008.

This PR makes the code correctly check if a progress bar has been installed in dock.

I'm not sure the exact condition to trigger the crash, and it is weird that there isn't much people seeing it. But I'm seeing it on my machine, and I can verify this PR fixes it on my machine.

Checklist

Release Notes

Notes: Fix crash when calling setProgressBar on macOS

@codebytere codebytere changed the title Fix crash when calling setProgressBar on macOS fix: crash when calling setProgressBar on macOS Jan 15, 2019
@zcbenz zcbenz force-pushed the fix-progress-bar-crash branch from af1b0b9 to 0fd7979 Compare January 21, 2019 02:58
@zcbenz zcbenz force-pushed the fix-progress-bar-crash branch from 0fd7979 to 627e8e8 Compare January 23, 2019 02:17
@codebytere codebytere merged commit 758d709 into master Feb 4, 2019
@release-clerk
Copy link
release-clerk bot commented Feb 4, 2019

Release Notes Persisted

Fix crash when calling setProgressBar on macOS

@trop
Copy link
Contributor
trop bot commented Feb 4, 2019

I have automatically backported this PR to "3-1-x", please check out #16726

@trop
Copy link
Contributor
trop bot commented Feb 4, 2019

I have automatically backported this PR to "4-0-x", please check out #16727

@trop trop bot removed the target/4-0-x label Feb 4, 2019
@trop
Copy link
Contributor
trop bot commented Feb 4, 2019

I have automatically backported this PR to "5-0-x", please check out #16728

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0