[
https://issues.apache.org/jira/browse/PROTON-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953901#comment-16953901
]
Lukas commented on PROTON-2116:
-------------------------------
https://issues.apache.org/jira/browse/PROTON-2121 is a possible duplicate of
this issue - please verify the test case described in PROTON-2121 and if it's
not possible to reproduce the issue with the version 0.30.0 please close
PROTON-2121 as duplicate.
I tried to quickly backport the changes in 8c2e66c to 0.28.0 but I'm still
experiencing the file descriptor leak.
> Memory leak in python client
> ----------------------------
>
> Key: PROTON-2116
> URL: https://issues.apache.org/jira/browse/PROTON-2116
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
> Affects Versions: proton-c-0.29.0
> Reporter: Clifford Jansen
> Assignee: Clifford Jansen
> Priority: Major
> Fix For: proton-c-0.30.0
>
> Attachments: leak.py
>
>
> The Python client leaks transports and selectables. When using the
> BlockingConnection classes, Containers, Collectors and other runtime class
> objects can also leak as additional referents.
> To reproduce, run the test case leak.py against the example broker. Kill and
> restart the broker repeatedly. The value of gc.get_objects() keeps increasing.
> Breaking the circular references between transports and selectables prevents
> these leaks.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
