#518 closed defect (fixed)
Growing memory usage in PJSUA-LIB
Reported by: | bennylp | Owned by: | bennylp |
---|---|---|---|
Priority: | normal | Milestone: | release-1.0-rc1 |
Component: | pjsua-lib | Version: | trunk |
Keywords: | Cc: | ||
Backport to 1.x milestone: | Backported: |
Description (last modified by bennylp)
Still some operations in PJSUA-LIB use the global pool which will not be destroyed until the application quits.
Change History (5)
comment:1 Changed 17 years ago by bennylp
- Milestone changed from release-0.9.0 to Known-Issues
comment:2 Changed 16 years ago by bennylp
- Milestone changed from Known-Issues to release-0.9.5
comment:3 Changed 16 years ago by bennylp
- Description modified (diff)
- Summary changed from Memory leak in PJSUA-LIB to Growing memory usage in PJSUA-LIB
comment:4 Changed 16 years ago by bennylp
- Resolution set to fixed
- Status changed from new to closed
comment:5 Changed 16 years ago by bennylp
In r2134:
only destroy the account and buddy pools after busy_sleep() is done, otherwise when unregistration callback is called, the callback will access accounts which are no longer valid because the pool has been destroyed
Note: See
TracTickets for help on using
tickets.
In r2130: