[asterisk-bugs] [JIRA] (ASTERISK-24238) Double free or corruption (!prev) - moh_files_generator

[Rusty Newton (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Newton updated ASTERISK-24238:
------------------------------------

    Assignee: Matt Jordan  (was: Lee Webb)
      Status: Triage  (was: Waiting for Feedback)

> Double free or corruption (!prev) - moh_files_generator
> -------------------------------------------------------
>
>                 Key: ASTERISK-24238
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24238
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_musiconhold
>    Affects Versions: 1.8.20.1
>         Environment: CentOS 6.5 x86_64
>            Reporter: Lee Webb
>            Assignee: Matt Jordan
>            Severity: Critical
>
> Hi Team,
> We've recently experienced what I'm hoping is a once off Asterisk crash while using 1.8.20.1.
> {code}
> Aug 15 01:13:46 gsdcvoice07 asterisk: *** glibc detected *** /home/asterisk/asterisk-bin/sbin/asterisk: double free or corruption (!prev): 0x00000000021454d0 ***
> {code}
> The GDB back trace contained the following
> {code}
> Program terminated with signal 6, Aborted.
> #0  0x00007f1ab1eb0925 in raise () from /lib64/libc.so.6
> Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.132.el6_5.2.x86_64 keyutils-libs-1.4-4.el6.x86_64 krb5-libs-1.10.3-15.el6_5.1.x86_64 libcom_err-1.41.12-18.el6.x86_64 libgcc-4.4.7-4.el6.x86_64 libselinux-2.0.94-5.3.el6_4.1.x86_64 libstdc++-4.4.7-4.el6.x86_64 libxml2-2.7.6-14.el6_5.2.x86_64 mysql-libs-5.5.38-1.el6.remi.x86_64 ncurses-libs-5.7-3.20090208.el6.x86_64 openssl-1.0.1e-16.el6_5.14.x86_64 zlib-1.2.3-29.el6.x86_64
> (gdb) bt
> #0  0x00007f1ab1eb0925 in raise () from /lib64/libc.so.6
> #1  0x00007f1ab1eb2105 in abort () from /lib64/libc.so.6
> #2  0x00007f1ab1eee837 in __libc_message () from /lib64/libc.so.6
> #3  0x00007f1ab1ef4166 in malloc_printerr () from /lib64/libc.so.6
> #4  0x00007f1ab1ef6ca3 in _int_free () from /lib64/libc.so.6
> #5  0x00000000004b6f9b in __frame_free (frame=0x21454d0, cache=1) at frame.c:370
> #6  ast_frame_free (frame=0x21454d0, cache=1) at frame.c:382
> #7  0x00007f1aadcec5ef in moh_files_generator (chan=0x7f1a1c075268, data=<value optimized out>, len=<value optimized out>, samples=<value optimized out>) at res_musiconhold.c:392
> #8  0x000000000046eb60 in generator_force (data=0x7f1a1c075268) at channel.c:3120
> #9  0x000000000047195f in __ast_read (chan=0x7f1a1c075268, dropaudio=<value optimized out>) at channel.c:3876
> #10 0x0000000000476c5c in ast_read (chan=0x7f1a1c075268, timeout_ms=1000, cond=0x7f1a75619f45 <agent_cont_sleep>, data=0x201f320) at channel.c:4336
> #11 ast_safe_sleep_conditional (chan=0x7f1a1c075268, timeout_ms=1000, cond=0x7f1a75619f45 <agent_cont_sleep>, data=0x201f320) at channel.c:1870
> #12 0x00007f1a7561f55d in login_exec (chan=0x7f1a1c075268, data=<value optimized out>) at chan_agent.c:2183
> #13 0x00000000004e9185 in pbx_exec (c=0x7f1a1c075268, app=0x1ff6a30, data=0x7f1a68296680 "500241051,s") at pbx.c:1446
> #14 0x00000000004f3b3c in pbx_extension_helper (c=0x7f1a1c075268, con=0x0, context=0x7f1a1c0757c0 "agent-login", exten=0x7f1a1c075810 "s", priority=9, label=0x7f1a1c0757c0 "agent-login", callerid=0x7f1a1c0e7ad0 "61295898015", 
>     action=E_SPAWN, found=0x7f1a68298cfc, combined_find_spawn=1) at pbx.c:4489
> #15 0x00000000004fa222 in ast_spawn_extension (c=0x7f1a1c075268, args=0x0) at pbx.c:5127
> #16 __ast_pbx_run (c=0x7f1a1c075268, args=0x0) at pbx.c:5230
> #17 0x00000000004fbb72 in pbx_thread (data=<value optimized out>) at pbx.c:5571
> #18 0x000000000053298c in dummy_start (data=<value optimized out>) at utils.c:1010
> #19 0x00007f1ab12779d1 in start_thread () from /lib64/libpthread.so.0
> #20 0x00007f1ab1f66b5d in clone () from /lib64/libc.so.6
> {code}
> Unfortunately we didn't have DONT_OPTIMISE as a compilation option so I can't provide any better information at this time & this is the first instance of the issue we've seen so I can't be certain whether it might happen again.
> Interestingly on the same platform we're also occasionally deadlocking issues within Asterisk too which I'm trying to troubleshoot, however I'm not sure whether that might be related.
> Any help would be appreciated.



--
This message was sent by Atlassian JIRA
(v6.2#6252)