[
https://issues.apache.org/jira/browse/PROTON-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816529#comment-15816529
]
ASF GitHub Bot commented on PROTON-1312:
----------------------------------------
Github user ssorj commented on a diff in the pull request:
https://github.com/apache/qpid-proton/pull/93#discussion_r95481951
--- Diff: proton-c/bindings/python/proton/__init__.py ---
@@ -2581,6 +2581,9 @@ def close(self):
"""
self._update_cond()
pn_connection_close(self._impl)
+ if hasattr(self, '_session_policy'):
--- End diff --
Gotcha, consistent with the existing code.
> BlockingConnection leaks Proton-C memory
> ----------------------------------------
>
> Key: PROTON-1312
> URL: https://issues.apache.org/jira/browse/PROTON-1312
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
> Affects Versions: 0.9, 0.15.0
> Reporter: Cliff Jansen
> Assignee: Cliff Jansen
> Labels: leak, reproducer
> Fix For: 0.17.0
>
> Attachments: ml8.py
>
>
> The attached program leaks the underlying connection (the C proton
> object) associated with the BlockingConnection on each loop iteration
> on proton 0.9 as used by Satellite. Without the receiver, it cleans
> up fine.
> On master, the program leaks both the reactor and the connection
> associated with the BlockingConnection for each loop. The receiver
> creation can be commented out and it still leaks both objects.
> Other objects may leak too (presumably session), but I have not
> examined further.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
