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

Ken Giusti commented on PROTON-2546:
------------------------------------

I've been debugging this a bit and think that the pn_raw_connection is being 
leaked.

-----------------------------------------------------
Suppressions used:
  count      bytes template
      *2       3072 ^pn_raw_connection$*
      6        384 sys_mutex
    390     408014 /libpython3.*.so
-----------------------------------------------------

SUMMARY: AddressSanitizer: 896 byte(s) leaked in 18 allocation(s).

 

I can reproduce these leaks by shutting down the skupper-router while there is 
at least one active pn_raw_connection. I shut down the router by sending a 
SIGTERM to it via kill.  In this case the router does not attempt to call 
pn_raw_connection_close() and wait for the disconnect.  Instead the shutdown 
code calls pn_proactor_free() and expects any outstanding raw connection memory 
to be freed by that.

Is this assumption correct?

If no raw connections are present at shutdown these leaks do not occur.

 

> Leak of raw connection pn_event
> -------------------------------
>
>                 Key: PROTON-2546
>                 URL: https://issues.apache.org/jira/browse/PROTON-2546
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: proton-c-0.38.0
>            Reporter: Ken Giusti
>            Assignee: Andrew Stitcher
>            Priority: Major
>
> See: 
> [https://github.com/skupperproject/skupper-router/issues/469|https://github.com/skupperproject/skupper-router/issues/469?]
> This leak appeared on main about five days ago:
> https://github.com/skupperproject/skupper-router/runs/6489086985?check_suite_focus=true#step:26:1757
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

Reply via email to