-
Bug
-
Resolution: Fixed
-
P3
-
17, 18
-
b21
-
os_x
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8278004 | 17.0.3-oracle | Anton Tarasov | P3 | Resolved | Fixed | b01 |
| JDK-8277858 | 17.0.2 | Anton Tarasov | P3 | Resolved | Fixed | b07 |
| JDK-8287657 | 11.0.17-oracle | Dmitry Markov | P3 | Resolved | Fixed | b01 |
| JDK-8288266 | 8u351 | Dmitry Markov | P3 | Resolved | Fixed | b01 |
+[CommonComponentAccessibility createWithParent:accessible:role:index:withEnv:withView:isWrapped:]
the isWrapped arg is used to create an a11y element which is wrapped into an object that does not have direct peer in Java like ListRowAccessibility, TableRowAccessibility. In the current implementation these objects leak, because when the wrapped element is created (isWrapped == YES), the native pointer to the element is rewritten in the associated java peer (the 'accessible' arg) and the element object is then released via the CFRetainedResource mechanism. However the wrapping object (ListRowAccessibility, TableRowAccessibility) is never released.
The wrapping logic should thus be reimplemented.
- backported by
-
JDK-8277858 CommonComponentAccessibility.createWithParent isWrapped causes mem leak
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk17u/a1049e87
-
Commit
openjdk/jdk/574f8903
-
Review
openjdk/jdk17u/307
-
Review
openjdk/jdk/6081