-
Notifications
You must be signed in to change notification settings - Fork 19
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
proton raw connection event leak #469
Comments
@astitcher Happened again on main, so probably caused by Proton change.
The suppressions for Proton types in the router currently are skupper-router/tests/lsan.supp Lines 21 to 27 in e43f50f
skupper-router/tests/lsan.supp Lines 78 to 89 in e43f50f
|
@jiridanek Hmm, that does look lik e it's caused by that change but I can't see anything different about this use compared to others that do work. |
@jiridanek @astitcher if this is likely a proton bug is there a proton JIRA we can link to? |
This backtrace is coming from the router - it is not a reactor-based traceback: 55: ================================================================= |
Proton JIRA: https://issues.apache.org/jira/browse/PROTON-2546 |
pni_class_new
with proton main
Actually, this leak is coming from the reactor code, which is deprecated but still used by a few test clients. The other leak (see #469 (comment)) is actually the one for concern. I'll open a separate bug to track the reactor deprecation issue. |
FYI #482 will track removal of the leaky reactor stuff |
This should be fixed by apache/qpid-proton@e2fa36f |
Closing this issue |
https://github.com/jiridanek/skupper-router/runs/6430169530?check_suite_focus=true#step:26:9200
I will have to check if maybe I broke this (the CI link goes to my PR), but I think that is unlikely and this is caused by Proton change.
The text was updated successfully, but these errors were encountered: