[ 
https://issues.apache.org/jira/browse/DISPATCH-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17340795#comment-17340795
 ] 

ASF subversion and git services commented on DISPATCH-1679:
-----------------------------------------------------------

Commit dd319e527127fc2d13ad8ff11b9a07d265f2309f in qpid-dispatch's branch 
refs/heads/1.16.x from Ken Giusti
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=dd319e5 ]

DISPATCH-2046: prevent crash when accessing connector pointer
DISPATCH-1679: fix qd_connector_t leak
DISPATCH-1917: fix race when accessing connector->conn_msg buffer

This closes #1176

(cherry picked from commit 8545a425cd8ee86beffdc97464fd4d4a20618a05)


> leak: qd_connector_t and qd_timer_t
> -----------------------------------
>
>                 Key: DISPATCH-1679
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1679
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Routing Engine
>    Affects Versions: 1.12.0
>            Reporter: Ken Giusti
>            Assignee: Ken Giusti
>            Priority: Major
>              Labels: leak
>             Fix For: Backlog
>
>
> Every unit test that involves use of a connector leaks the connector and a 
> related qd_timer_t.  These leak warnings overwhelm other warnings in the test 
> output.
> The qd_connector_t is reference counted.  It also contains a qd_timer_t.  
> From initial debug the reference count is never dropping below 1.
> It appears that every time the timer is scheduled the refcount is 
> incremented.  This appears to be an attempt to prevent the deletion of the 
> qd_connector_t while the timer is outstanding.  This appears likely to be the 
> source of the outstanding ref count.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to