It's somewhat random, but the memory that gets corrupted is in unallocated memory. The OS X malloc checks checksums on freed memory and if it was modified after free, it will complain next malloc. This is quite reproducible for me. I can't imagine it's PA, since setting the conference level to zero causes the same problem, so the PA implementation is sill getting good audio. Whether I disconnect the sound input from the bridge or set the volume to zero, the bug appears. Speaking of which, does PJSIP do some sort of gain control? We are having issues what something doing gain control that amplifies background noise when a client isn't talking. I'm not sure if Asterisk is doing it, PJSIP or PA. Norman Franke ASD, Inc. On Jan 4, 2008, at 2:05 AM, Benny Prijono wrote: > I tried to reproduce it here (on a Windows machine) but it didn't > happen, unfortunately. So maybe this behavior is specific to PA > implementation on Mac? > > Which part of memory got corrupted? And where the crash is located? > > cheers, > -benny > > Norman Franke wrote: >> I have no_vad set to true, and it still happens if I set >> ec_tail_len = >> 0. Setting no_vad = false still causes the problem to appear. Is >> there >> some other silence detection in pjmedia? >> >> Norman Franke >> ASD, Inc. >> >> On Jan 3, 2008, at 6:38 PM, Norman Franke wrote: >> >>> More on this issue. If I just use the mute switch on my headset, >>> I can >>> reproduce the crash. It appears that PJSIP is doing something odd if >>> it detects silence from the mic. >>> >>> Norman Franke >>> ASD, Inc. >>> >>> >>> >>> On Jan 3, 2008, at 6:04 PM, Norman Franke wrote: >>> >>>> I'm not entirely sure PJSIP is causing this, but here is what's >>>> happening: >>>> >>>> 1. I establish a SIP call somewhere. >>>> 2. Create a recorder instance, connect to the call and sound input >>>> device. >>>> 3. Mute the audio (i.e. the main input device is disconnected from >>>> the recorder & call.) >>>> 4. At this point, memory corruption happens constantly in the >>>> background. >>>> 5. Unmuting (i.e. reconnecting the sound input device to the >>>> call and >>>> recorder) stops the memory corruption from continuing. >>>> >>>> Any ideas on how to track this one down? >>>> >>>> Norman Franke >>>> ASD, Inc. > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080104/44eba487/attachment.html
