-
Notifications
You must be signed in to change notification settings - Fork 15.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
fix: correctly destroy spellcheck client #16448
Conversation
We should backport this to 3-0-x also, right? |
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.
LGTM with minor changes, thanks!
@nitsakh since |
0432d62
to
b879de7
Compare
f411cd2
to
b3d1a24
Compare
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.
LGTM, thanks!
Release Notes Persisted
|
I was unable to backport this PR to "4-0-x" cleanly; |
I was unable to backport this PR to "3-1-x" cleanly; |
Description of Change
This change addresses #15459.
The spellcheck client wasn't destroyed when the renderer goes away.
This change adds an observer which takes care of the destruction.
Checklist
npm test
passesRelease Notes
Notes: Fixed
webFrame.setSpellCheckProvider
memory leak