Ozzyboshi left a comment (kamailio/kamailio#4503)
Hello again,
I would like to share the results of my investigation.
As a first step, I built Kamailio with a larger MAX_REPLY_SIZE to allow me to
inspect stuck transactions.
It would be nice to have this value configurable, but there is a problem: in
several parts of the code there are local arrays sized using MAX_REPLY_SIZE,
and if the value is too large the stack memory is not sufficient.
Aside from this limitation, increasing the value allowed me to capture some
Call-IDs associated with memory leaks. All of them had one particular thing in
common: an error that caused our Kamailio configuration file to execute the
drop; instruction.
It seems that when drop; is executed after branching, the function
wait_handler() (where I would expect the SHM memory associated with the
transaction cell to be freed) is not executed, resulting in a memory leak.
So I would like to ask the community whether this could explain the memory leak
I’m seeing.
If I remove the drop; instruction, everything works as expected: when calls
end, SHM memory goes back to almost zero.
Has anyone encountered a similar issue?
What can I do to continue this investigation?
How is it possible that the drop; instruction causes this behavior?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4503#issuecomment-3647352891
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4503/[email protected]>
_______________________________________________
Kamailio - Development Mailing List -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the
sender!
