| 11:15.07 | *** join/#asterisk-bugs file (~file@asterisk/developer-and-muffin-lover/file) |
| 11:15.07 | *** mode/#asterisk-bugs [+o file] by ChanServ |
| 11:22.56 | *** join/#asterisk-bugs caio1982 (~caio1982@CAcert-br/caio1982) |
| 11:45.14 | *** join/#asterisk-bugs leifmadsen (~Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 11:45.14 | *** mode/#asterisk-bugs [+o leifmadsen] by ChanServ |
| 12:47.37 | *** join/#asterisk-bugs eliel (~eliels@201.234.94.226) |
| 15:20.11 | *** join/#asterisk-bugs infobot (ibot@rikers.org) |
| 15:20.11 | *** topic/#asterisk-bugs is Asterisk Bugs Discussion -=- http://issues.asterisk.org/ -=- http://asterisk.org/developers/bug-guidelines - Discussions not related to reported issues should be in #asterisk -=- Test bugs marked Ready For Testing! -=- http://xkcd.org/583/ |
| 15:26.20 | pabelanger | waves at infobot |
| 15:53.52 | dwayne | leifmadsen, minor bug in M17078 ... working on it now |
| 15:54.03 | leifmadsen | dwayne: awesome thanks! |
| 16:02.55 | *** join/#asterisk-bugs TheDavidFactor (~chatzilla@nc-71-0-16-133.dhcp.embarqhsd.net) |
| 16:06.32 | seanbright | so with -g and 'ulimit -c unlimited' |
| 16:06.39 | seanbright | why would asterisk not generate a core file? |
| 16:11.08 | *** join/#asterisk-bugs elguero (~miguel323@ns1.nashuacs.com) |
| 16:14.12 | putnopvut | seanbright: permission issue? |
| 16:14.22 | putnopvut | That's the only thing that comes to mind immediately. |
| 16:15.46 | seanbright | putnopvut: you're probably correct. thanks. |
| 16:25.33 | seanbright | putnopvut: that was it. running asterisk as non-root :-( |
| 16:25.37 | seanbright | and cwd was / |
| 16:25.52 | putnopvut | Ah, cool beans. |
| 16:26.02 | putnopvut | Sucks that you don't have a core dump though... |
| 16:26.06 | seanbright | agreed. |
| 16:26.22 | seanbright | went 4.5 straight days without a crash... and then... BOOM |
| 16:26.27 | seanbright | 1.6.1 HEAD |
| 16:26.32 | seanbright | so we'll have something to look at next week |
| 16:30.30 | seanbright | kernel.core_pattern ftw |
| 17:15.06 | *** join/#asterisk-bugs corretico (~laguilar@201.201.46.106) |
| 17:23.18 | *** join/#asterisk-bugs elguero (~miguel323@ns1.nashuacs.com) |
| 17:38.27 | Deeewayne | R611 |
| 17:38.32 | MuffinMan | [R611] Fix issue 17078: MixMonitor records shorter files than the call duration. [Pending] Submitted by dhubbard => https://reviewboard.asterisk.org/r/611/ |
| 17:39.00 | Deeewayne | The_Boy_Wonder's question regarding StopMixMonitor may have uncovered another bug |
| 17:39.31 | Deeewayne | every time stopmixmonitor is called, the recording stops but the thread does not die until the channel hangs up |
| 17:39.52 | Deeewayne | if you start and stop mixmonitor in a single call, mixmonitor threads will accumulate |
| 17:40.04 | The_Boy_Wonder | Deeewayne: is this with or without the patch? |
| 17:40.07 | Deeewayne | they are all just waiting for the destruction_ok signal ... would this be a bug? |
| 17:40.45 | Deeewayne | The_Boy_Wonder, looks like both in the code but I'm verifying that now. I don't see why this would be related to the patch since it is after the while-loop that the patch modifies |
| 17:41.31 | Deeewayne | the threads don't leak beyond the life of the call, but they do pile up during the life of the call |
| 17:41.37 | Deeewayne | bug? |
| 17:41.38 | The_Boy_Wonder | Deeewayne: i fixed that a few months ago, and i made that comment because i remembered the ordering of that code was important for some reason |
| 17:42.25 | The_Boy_Wonder | ah |
| 17:42.59 | Deeewayne | they will wait in ast_cond_wait(mixmonitor_ds->destruction_condition) |
| 17:43.02 | The_Boy_Wonder | its the "STATUS_RUNNING" check i bet, that got nested in that other statement |
| 17:44.18 | Deeewayne | are you referring to the patch? |
| 17:44.48 | The_Boy_Wonder | Deeewayne: yeah, I don't think that is going to work right. those checks were supposed to come before the read_frame call to break out correctly |
| 17:44.56 | The_Boy_Wonder | that code is really tricky |
| 17:46.29 | Deeewayne | hrm, well maybe putting the trigger_wait in the block before continue and leaving the audiohook.status check where it is will work |
| 17:47.44 | Deeewayne | I'm not sure why that matters though, I'm going to try to reproduce it w/o the patch |
| 17:52.05 | Deeewayne | The_Boy_Wonder, I'm seeing the threads accumulate during the life of the call with and without the patch in R611 |
| 17:52.26 | The_Boy_Wonder | well, that sucks |
| 17:52.43 | The_Boy_Wonder | what revision? |
| 17:52.50 | The_Boy_Wonder | Deeewayne: ^ |
| 17:53.24 | Deeewayne | I don't want to tell you |
| 17:53.39 | Deeewayne | I just verified it on 1.4.26, but the code in trunk looks like it would do the same |
| 17:54.03 | Deeewayne | I need a bit of time to reproduce it on trunk |
| 17:54.59 | Deeewayne | in trunk, it is still going to break out of that while-loop and wait for the destruction_ok condition |
| 17:56.46 | The_Boy_Wonder | well, i know that issue with the thread was resolved sometime recently |
| 17:57.02 | Deeewayne | ok, I'll see what I can do w/ trunk |
| 17:58.05 | Deeewayne | The_Boy_Wonder, would have fixed that in 1.4? It'd be easier for me to reproduce it w/ the lastest of 1.4 |
| 17:58.25 | The_Boy_Wonder | yes |
| 17:58.35 | The_Boy_Wonder | i'll find the revision real quick |
| 17:58.36 | The_Boy_Wonder | to make sure |
| 17:59.10 | The_Boy_Wonder | 1.4 r230508 |
| 18:01.48 | Deeewayne | I'm building 1.4 r257641 right now ... need 5 minutes to try to reproduce |
| 18:03.28 | seanbright | starts counting |
| 18:05.29 | Deeewayne | The_Boy_Wonder, you are right, you fixed that |
| 18:05.50 | Deeewayne | so, I'll retest my patch and respond to R611 |
| 18:06.19 | The_Boy_Wonder | Deeewayne: cool, looking at what was done, it probably wont' affect it. i just hate touching that code. |
| 18:06.45 | Deeewayne | yeah, I think my patch is safe, but I'll verify |
| 18:06.51 | Deeewayne | thanks |
| 18:07.55 | Deeewayne | A230508 |
| 18:09.13 | Deeewayne | what's the command to get revision details from infobot? |
| 18:09.26 | Qwell | asterisk commit 230508 |
| 18:09.29 | Qwell | commit asterisk 230508 |
| 18:09.30 | Qwell | that one |
| 18:09.32 | MuffinMan | [230508] Committed by dvossel on 2009-11-19T21:22:46.275352Z: fixes MixMonitor thread not exiting when StopMixMonitor is used |
| 18:09.32 | MuffinMan | .. |
| 18:09.32 | MuffinMan | ..(closes issue #16152) |
| 18:09.32 | MuffinMan | ..Reported by: AlexMS |
| 18:09.32 | MuffinMan | ..Patches: |
| 18:09.34 | MuffinMan | .. stopmixmonitor_1.4.diff uploaded by dvossel (license 671) |
| 18:09.37 | MuffinMan | ..Tested by: dvossel, AlexMS |
| 18:09.40 | MuffinMan | .. |
| 18:09.41 | Deeewayne | Qwell, thanks |
| 18:09.42 | MuffinMan | ..Review: https://reviewboard.asterisk.org/r/424/ |
| 18:09.44 | MuffinMan | .. |
| 18:09.46 | MuffinMan | .. http://svn.digium.com/view/asterisk?view=rev&revision=230508 |
| 18:09.59 | Deeewayne | I'll ask infobot privately next time |
| 18:20.58 | Deeewayne | yay everything is happy now |
| 18:31.42 | *** join/#asterisk-bugs SuGaO (~SuGaO@189.89.145.254) |
| 18:35.55 | SuGaO | Olá Senhores |
| 18:35.56 | SuGaO | Algúem lá passou por um problema desse: |
| 18:35.56 | SuGaO | ERROR[7360]: chan_dahdi.c:8803 dahdi_pri_error: !! Got reject for frame 75, but we have nothing -- resetting! |
| 18:35.56 | SuGaO | Estou usando Dahdi 2.3.0 + Asterisk 1.4.30 Lib-pri 1.4.10.2 |
| 19:51.47 | pabelanger | m17192 |
| 19:51.49 | MuffinMan | [new] [Asterisk] Channels/chan_sip/General 0017192: Phone keeps ringing when hangup between 'NOTIFY' and 'Status: 180 Ringing' reported by ronaldderksen https://issues.asterisk.org/view.php?id=17192 |
| 19:52.03 | pabelanger | giving this a test now, since I have the gear next to me. |
| 20:01.21 | *** join/#asterisk-bugs corretico (~laguilar@201.201.46.106) |
| 20:05.52 | pabelanger | can't reproduce with trunk, moving to 1.6.2 |
| 20:24.22 | *** join/#asterisk-bugs dwayne (~dwayne@c-71-207-214-190.hsd1.al.comcast.net) |
| 20:48.38 | *** join/#asterisk-bugs TheDavidFactor (~chatzilla@nc-71-0-16-133.dhcp.embarqhsd.net) |
| 20:50.01 | *** join/#asterisk-bugs dwayne (~dwayne@75-150-14-49-Atlanta.hfc.comcastbusiness.net) |
| 20:56.56 | pabelanger | So, I'm out for the day. But I _think_ 17192 is an issue. It is hard to reproduce because the events happen so fast on my local system. I'm going to see if I can understand more about the destruction of SIP dialog's. |
| 20:58.25 | Qwell | M17196 |
| 20:58.27 | MuffinMan | [new] [Asterisk] Applications/app_directory 0017196: Stuck in vicious loop reported by supertle https://issues.asterisk.org/view.php?id=17196 |
| 20:58.32 | Qwell | oh, he's not here |
| 20:58.36 | Qwell | nevermind |
| 21:39.03 | *** join/#asterisk-bugs pabelanger_ (~pabelange@CPE004010100002-CM00159a090f12.cpe.net.cable.rogers.com) |
| 22:31.53 | *** join/#asterisk-bugs dwayne (~dwayne@c-71-207-214-190.hsd1.al.comcast.net) |
| 22:44.41 | *** join/#asterisk-bugs elguero (~miguel323@ns1.nashuacs.com) |
| 23:55.15 | *** join/#asterisk-bugs dwayne (~dwayne@75-150-14-49-Atlanta.hfc.comcastbusiness.net) |
| 23:55.34 | *** join/#asterisk-bugs elguero (~miguel323@ns1.nashuacs.com) |