Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
P3
-
Resolution: Fixed
-
Affects Version/s: 8, 11, 14
-
Fix Version/s: 14
-
Component/s: security-libs
-
Subcomponent:
-
Resolved In Build:b08
-
CPU:generic
-
OS:os_x
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8241317 | 13.0.3 | Matthias Baesken | P3 | Resolved | Fixed | b01 |
JDK-8230009 | 11.0.6-oracle | Robert Mckenna | P3 | Resolved | Fixed | b01 |
JDK-8229404 | 11.0.5 | Matthias Baesken | P3 | Resolved | Fixed | b03 |
Description
In KeystoreImpl.m we call CFDataCreate at one place.
According to
https://developer.apple.com/documentation/corefoundation/1542359-cfdatacreate?language=objc
the return value of CFDataCreate is
"A new CFData object, or NULL if there was a problem creating the object. Ownership follows the The Create Rule."
Following the "Create Rule" we have to release the return value to avoid leaks.
According to
https://developer.apple.com/documentation/corefoundation/1542359-cfdatacreate?language=objc
the return value of CFDataCreate is
"A new CFData object, or NULL if there was a problem creating the object. Ownership follows the The Create Rule."
Following the "Create Rule" we have to release the return value to avoid leaks.
Attachments
Issue Links
- backported by
-
JDK-8229404 fix CFData object leak in macosx KeystoreImpl.m
-
- Resolved
-
-
JDK-8230009 fix CFData object leak in macosx KeystoreImpl.m
-
- Resolved
-
-
JDK-8241317 fix CFData object leak in macosx KeystoreImpl.m
-
- Resolved
-