JDK-8225805 : Java Access Bridge does not close the logger
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.accessibility
  • Affected Version: 11,13
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-06-14
  • Updated: 2020-12-14
  • Resolved: 2019-09-11
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 11 JDK 14 Other
11.0.11-oracleFixed 14 b16Fixed openjdk8u292Fixed
Related Reports
Relates :  
It is necessary to close AccessBridge logger in WinAccessBridge destructor.
Fix Request (8u): Backport to 8u requested because this patch is submitted to 11 and relevant code (and possible problem) in 8u is the same. Patch applies cleanly after changing file path. See testing details in previous comment. 8u patch with changed path: https://cr.openjdk.java.net/~akasko/jdk8u/8225805/webrev.00/

Fix Request (11u): Backport to 11u requested because it is a part of 11.0.11-oracle. Patch applies cleanly. Testing: with JAWS and ProcMon was unable to reproduce the problem with windows_access_bridge.log closure. It is explained in the review thread ( http://mail.openjdk.java.net/pipermail/awt-dev/2019-September/015375.html ) that it can happen if JAWS exits abnormally (and destructors inside it won't run). Killing JAWS with taskkill /f is not enough for that. Verified, that patch doesn't break anything with JAWS and log file is written and closed correctly.

URL: https://hg.openjdk.java.net/jdk/jdk/rev/5028ccc17275 User: psadhukhan Date: 2019-09-25 09:20:40 +0000

URL: https://hg.openjdk.java.net/jdk/client/rev/5028ccc17275 User: pbansal Date: 2019-09-11 10:37:08 +0000