Summary:	ASTERISK-05190: IAX deadlock
Reporter:	wunderkin (wunderkin)	Labels:
Date Opened:	2005-09-29 12:52:50	Date Closed:	2011-06-07 14:00:57
Priority:	Blocker	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) gdb-iax
Description:	I think this deadlock is caused by IAX2.  I did this testing before the manager fix.  I changed to using call files.  I was successfully testing using 4 full PRIs and then changed to using 2 full PRIs and 2 full PRIs worth of IAX calls.  It only started to deadlock when I started using IAX2. This is the only deadlock so far related to this issue.  I have started trying to cut down on the number of IAX channels since it seems to be causing audio clipping and missing audio.
Comments:	By: Clod Patry (junky) 2005-10-04 22:18:07 Just to make sure isnt related, could you try latest HEAD, cause like you know, a lot of manager patches was commited recently. Thanks. By: wunderkin (wunderkin) 2005-10-05 13:18:03 I'm not very sure how easily this can be replicated.  I'm not using IAX anymore in production either.  I tried to replicate it just after Mark was helping me with the manager crash but nothing came out of the test. I can keep testing after production hours to see if I can replicate it, but it is going to be rough to get someone to look at it WHILE it is happening. I looked at the backtrace and didn't see anything mentioning the manager.  I don't think I was using it at that time. By: Mark Spencer (markster) 2005-10-13 11:00:14 So to confirm this is no longer an issue for you? By: wunderkin (wunderkin) 2005-10-13 19:49:25 The only reason it isn't an issue is because I haven't been using it. :D Like I said, its probably something that won't be very easy to replicate so if you want to put this one on hold or something .. whatever you want to do - if there's nothing you can do from the backtrace and other information given. By: Clod Patry (junky) 2005-10-19 11:45:56 Im gonna suspend it for now, since it seems to not being an issue anymore for wunderkin. I would guess if there was a deadlock in IAX2, a lot of people would complain/report it anyways. If you got the same isssue, you or someone else. Let us know in #asterisk-bugs, we'll re-open that ticket. Thanks.