I ran into these while testing with SIPP and having memlog=1 :
kamailio[21826]: : <core> [mem/q_malloc.c:453]: qm_free(): BUG: qm_free: freeing already freed pointer (0x7f24869850f8), called
from <core>: parser/contact/parse_contact.c: free_contact(109), first free <core>: parser/contact/parse_contact.c: free_contact(109) - aborting
kamailio[21540]: : <core> [mem/q_malloc.c:453]: qm_free(): BUG: qm_free: freeing already freed pointer (0x7f4161b971c0), called
from <core>: data_lump_rpl.c: free_lump_rpl(107), first free <core>: data_lump_rpl.c: free_lump_rpl(107) - aborting
These two patches fix these two separate issues.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/753
-- Commit Summary --
* core: fix double free on clearing hdr
* core: fix double free on clearing lump
-- File Changes --
M data_lump_rpl.c (5)
M parser/hf.c (7)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/753.patchhttps://github.com/kamailio/kamailio/pull/753.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/753
Module: kamailio
Branch: master
Commit: 839cf89b02f8817156487a960ff62013e3cde530
URL: https://github.com/kamailio/kamailio/commit/839cf89b02f8817156487a960ff6201…
Author: Phil Lavin <phil.lavin(a)synety.com>
Committer: Phil Lavin <phil.lavin(a)synety.com>
Date: 2016-07-27T15:04:26+01:00
presentity: don't update terminated presentity entries in the database
- Fixes a race condition caused by, for example, the call being answered
at almost exactly the same time as the caller cancels. This causes
a terminated state to change back to completed. The dialog is then
removed from the database and the presentity entry stays in place
until it expires.
- This fix explicitly prevents terminated entries being updated as the
state machine in RFC 4235 prohibits this behaviour.
---
Modified: modules/presence/presentity.c
---
Diff: https://github.com/kamailio/kamailio/commit/839cf89b02f8817156487a960ff6201…
Patch: https://github.com/kamailio/kamailio/commit/839cf89b02f8817156487a960ff6201…
presentity: don't update terminated presentity entries in the database
- This fix is pull requested based on the stuff in pull request #724. That is because the stuff done here builds on that earlier work. #724 probably wants to be merged before this one.
- Fixes a race condition caused by, for example, the call being answered at almost exactly the same time as the caller cancels. This causes a terminated state to change back to completed. The dialog is then removed from the database and the presentity entry stays in place until it expires.
- This fix explicitly prevents terminated entries being updated as the state machine in RFC 4235 prohibits this behaviour.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/726
-- Commit Summary --
* presence: Always check if a record exists for this dialog before inserting
* presence: fix memory leak introduced by last commit
* presence: log when presentity is deleted due to already existing
* presentity: don't update terminated presentity entries in the database
-- File Changes --
M modules/presence/presentity.c (297)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/726.patchhttps://github.com/kamailio/kamailio/pull/726.diff
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/726