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
fix: potential crash calling tray.popUpContextMenu()
#39231
Conversation
8a961ff
to
0234c47
Compare
0234c47
to
dc1862a
Compare
ff08197
to
770bdff
Compare
770bdff
to
1b1e107
Compare
tray.popUpContextMenu
tray.popUpContextMenu()
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me based on the stack trace.
Release Notes Persisted
|
I was unable to backport this PR to "24-x-y" cleanly; |
I was unable to backport this PR to "25-x-y" cleanly; |
I have automatically backported this PR to "26-x-y", please check out #39313 |
fix: potential crash calling tray.popUpContextMenu
@codebytere has manually backported this PR to "25-x-y", please check out #40271 |
@codebytere has manually backported this PR to "24-x-y", please check out #40272 |
fix: potential crash calling tray.popUpContextMenu
Description of Change
Speculative fix for a crash i've been seeing in CI a fair bit recently, but haven't been able to repro locally. It looks like the ElectronMenuModel is going away before this callback is called. We use
base::Unretained
here which isn't safe if we can't guarantee lifetime which I don't think we can here.Sample Failure
Stacktrace
Checklist
npm test
passesRelease Notes
Notes: Fixed a potential crash when calling
tray.popUpContextMenu
on macOS.