Memory consumption of the invite session grows indefinitely if call is running for long period of time and with many re-INVITES

[pjsipbot]

2009-06-04 10:51:35: @bennylp created the issue on trac ticket 877

The invite session uses single memory pool to allocate memory pool for its session data (such as negotiated SDPs, remote target, etc.), and by design, memory blocks are not freed until the pool is released, and for the invite session, this only happens when the session is terminated (call is hung up). Unfortunately, if the call is running for long period of time and with many re-INVITES, this will grow the memory consumption almost indefinitely.

---

2009-06-11 17:18:21: @bennylp changed milestone from release-1.3 to release-1.4

---

2009-08-12 18:54:15: @bennylp changed status from new to closed

---

2009-08-12 18:54:15: @bennylp set resolution to fixed

---

2009-08-12 18:54:15: @bennylp commented

Fixed in r2869:

• introducing flip-flop pools in the pjsip_inv_session. There are two additional pools created, and one of them will be reset everytime SDP negotiation is done to release memory back to the OS

---

2009-08-14 14:24:16: @nanangizz commented

In r2879:

• Fixed bug flip-flop pools shouldn't be swapped when SDP negotiation fails.