Skip to content

CoreFoundation: correct an over-release in CFTimeZone #2196

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

Merged
merged 1 commit into from
Apr 30, 2019

Conversation

compnerd
Copy link
Member

We would release a value obtained through a CFDictionaryGetValue which
would result in the value being over-released as the returned object is
returned at +0. This fixes the use-after-free on Windows.

Thanks to Gwynne Raskind for identifying the mismanagement of the retain
counts!

We would release a value obtained through a `CFDictionaryGetValue` which
would result in the value being over-released as the returned object is
returned at `+0`.  This fixes the use-after-free on Windows.

Thanks to Gwynne Raskind for identifying the mismanagement of the retain
counts!
@compnerd
Copy link
Member Author

CC: @gwynne @millenomi

@millenomi
Copy link
Contributor

@swift-ci please test and merge

@compnerd
Copy link
Member Author

@swift-ci please test Linux platform

@compnerd compnerd merged commit ce11f4e into swiftlang:master Apr 30, 2019
@compnerd compnerd deleted the my-memory-is-not-your-memory branch April 30, 2019 04:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants