Skip to content

[3.6] bpo-34745: Fix asyncio sslproto memory issues (GH-12386) #12393

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

Closed

Conversation

fantix
Copy link
Contributor

@fantix fantix commented Mar 18, 2019

  • Fix handshake timeout leak in asyncio/sslproto, refs Fixes #220 sslproto memory issue MagicStack/uvloop#222
  • Break circular ref _SSLPipe <-> SSLProtocol
  • bpo-34745: Fix asyncio ssl memory leak
  • Break circular ref SSLProtocol <-> UserProtocol
  • Add NEWS entry
  • Dropped unit test whose base test is missing in 3.6 <-- Please kindly suggest

(cherry picked from commit f683f46)

https://bugs.python.org/issue34745

https://bugs.python.org/issue34745

* Fix handshake timeout leak in asyncio/sslproto, refs MagicStack/uvloop#222

* Break circular ref _SSLPipe <-> SSLProtocol

* bpo-34745: Fix asyncio ssl memory leak

* Break circular ref SSLProtocol <-> UserProtocol

* Add NEWS entry
@1st1
Copy link
Member

1st1 commented Mar 18, 2019

Dropped unit test whose base test is missing in 3.6 <-- Please kindly suggest

Can't we backport it?

@fantix
Copy link
Contributor Author

fantix commented Mar 18, 2019

For some reason, a lot of sslproto test code is missing on 3.6. Let me try to backport all of them later today.

@1st1
Copy link
Member

1st1 commented Mar 18, 2019

Oh, it's fine then, I'll merge as is.

@1st1
Copy link
Member

1st1 commented Mar 18, 2019

Hm, I guess only release manager can merge this in 3.6 now...

@ned-deily
Copy link
Member

3.6 is now in security-fix only support mode. As it does not appear that this change meets the criteria for inclusion in a security-fix-only branch, I am closing the PR.

@ned-deily ned-deily closed this May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants