| Summary: | ASTERISK-23091: possible memory leak in abstract jitterbuffer | ||||
| Reporter: | Martin Vit (festr) | Labels: | |||
| Date Opened: | 2014-01-03 07:05:51.000-0600 | Date Closed: | 2014-01-03 10:42:08.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Core/Jitterbuffer | ||
| Versions: | 11.4.0 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| Description: | main/jitterbuffer.c - void jb_reset(jitterbuf *jb) nulls whole jb structure which can contain unfreed jb->free frames in case someone calls this function while frames are still in memory. I found this issue in my voipmonitor project when I'm using asterisks jitterbuffer code so I'm not sure if the jb_reset in asterisk is called but at least I have found some calls in channel.c ast_jb_empty_and_reset which will call this in the middle of a call so I'm convinced that it must leak.
I suggest to empty all frames in jb->free and probably jb->frames in the jb_reset function in jitterbuffer.c | ||||
| Comments: | By: Michael L. Young (elguero) 2014-01-03 10:42:08.528-0600 Thanks for your report. You might want to check out the latest version, 11.7, as it looks like this was already fixed in ASTERISK-22467. | ||||