-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8272806: [macOS] "Apple AWT Internal Exception" when input method is changed #5211
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
Conversation
|
👋 Welcome back prr! A progress list of the required criteria for merging this PR into |
|
@prrace This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 13 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
|
/integrate |
|
Going to push as commit f681d65.
Your commit was automatically rebased without conflicts. |
There's a long eval in the bug report : https://bugs.openjdk.java.net/browse/JDK-8272806 but here's the summary
When focus is lost by the app a message is sent down to native setting a native reference to the input method to null
which is a sort of signal not to notify upwards anything to the input method (which internally will NPE if there's
no focused component as is the case after focus is lost).
But we aren't actually setting it to null because of a check for null which previously checked the wrapper for
the JNI ref was not null but is now obsolete. So just remove the check for null.
The steps to reproduce this bug are very manual and involve installing additional input methods and toggling them
at the system level. So I didn't see a way to write a useful regression test but if you follow the bug report steps you
should be able to verify the fix.
I've run all automated tests just for good measure and they all pass.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5211/head:pull/5211$ git checkout pull/5211Update a local copy of the PR:
$ git checkout pull/5211$ git pull https://git.openjdk.java.net/jdk pull/5211/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5211View PR using the GUI difftool:
$ git pr show -t 5211Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5211.diff