<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=6481937" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/henningw">@henningw</a><br>
Q: "Is the binding from Kamailio memory manager to library memory manager functionality (ortp_memory_functions etc..) not needed anymore?"</p>
<p>A: I found as least to edge case in oRTP where it was not using the specified memory allocation functions ...<br>
At this point I think it will be less problematic spawn threads from one or more dedicated processes in Kamailio, the worker processes will not interact with the libraries directly.<br>
This seems like a perfectly fine decision in terms of architecture and there will be no more bugs related to shared memory ...</p>
<p>Thank for pinpointing the unwanted modifications to the core</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/kamailio/kamailio/pull/1823#issuecomment-458246409">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AF36ZW51tAdo4LqWJTyzKYEp-HhTpOtZks5vH0E-gaJpZM4aUmOj">mute the thread</a>.<img src="https://github.com/notifications/beacon/AF36ZWRdEs5yInbYJOLpwJDfqUyWbqT_ks5vH0E-gaJpZM4aUmOj.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/kamailio/kamailio","title":"kamailio/kamailio","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/kamailio/kamailio"}},"updates":{"snippets":[{"icon":"PERSON","message":"@jchavanton in #1823: @henningw \r\nQ: \"Is the binding from Kamailio memory manager to library memory manager functionality (ortp_memory_functions etc..) not needed anymore?\"\r\n\r\nA: I found as least to edge case in oRTP where it was not using the specified memory allocation functions ...\r\nAt this point I think it will be less problematic spawn threads from one or more dedicated processes in Kamailio, the worker processes will not interact with the libraries directly.\r\nThis seems like a perfectly fine decision in terms of architecture and there will be no more bugs related to shared memory ...\r\n\r\nThank for pinpointing the unwanted modifications to the core "}],"action":{"name":"View Pull Request","url":"https://github.com/kamailio/kamailio/pull/1823#issuecomment-458246409"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/kamailio/kamailio/pull/1823#issuecomment-458246409",
"url": "https://github.com/kamailio/kamailio/pull/1823#issuecomment-458246409",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>