Re: [Ekiga-devel-list] Desperate for Ekiga/Opal deadlock fix, Trying to get my employer to offer a bounty

[Charlie Hedlin <charlie hedlin com>]

I just finished testing the fix, only to find out that it made it into 
the repository at nearly the same time...
Revision 2.120.2.31 of sipcon.cxx contains the exact change to the code 
I made but was testing prior to sending a patch.

Any chance call recording will get backported to Phobos?  My recording 
worked in 2.2.3 but not current Phobos.  I am adding a file media stream 
as a sink to the patches on the PCSS endpoint.

Thank you,
Charlie

Craig Southeren wrote:
> Damien Sandras wrote:
> > Le vendredi 18 mai 2007 à 09:16 +1000, Craig Southeren a écrit :
> > > Charlie Hedlin wrote:
> > > > I am sure I can fix the deadlock, but I have only been reading opal 
> > > > and ekiga code for a few weeks, and we want to move our transition 
> > > > to Linux forward as soon as possible.  We seem to be getting 20-40 
> > > > calls in prior to a deadlock, but that is a far cry from the 10k a 
> > > > day we will eventually place (We have 100 people on the phones).
> > > As I posted to the OPAL list last week, I was able to run OPAL with 
> > > 200 simultaneous calls without any problems. The total number of 
> > > calls completed was well over 100k. I'd be very suprised if the 
> > > problem is in the OPAL library
> >
> > I would be very surprised if it was in Ekiga itself. (I think Craig that
> > you should read the backtrace).
> >
> > [...]
> >
> > > > What would a reasonable bounty be for fixing this bug?  I am 
> > > > thinking we would need to be able to complete 50k calls without a 
> > > > deadlock to call it fixed.
> > > >
> > > > It is definately related to the OnReleased thread cleanup.  I 
> > > > placed a blocking mechanism in the control thread we have been 
> > > > using to operate the phone independant of the gui to make sure we 
> > > > weren't calling disconnect twice.
> > > Are you using CVS head, or some other version?
> >
> > Charlie explained he was using Phobos. I suggested him to try with CVS
> > HEAD.
>
> I apologise for not being clear in my original email.
>
> Both Ekiga and OPAL have been extensively tested and are used every 
> day my many people. If there was a problem that caused a crash after 
> 20 calls, I am sure that many other people would be reporting it.  
> Both Damien and I would make far more calls that that in any given day
>
> As such, I suggest that you test an unmodified version of Ekiga on 
> your system, and see if that has the same behaviour. If it does, then 
> we need to work out why what is happening. Damien and I will be able 
> to help you with that.
>
> If the problem does not occur with a standard Ekiga and OPAL, then it 
> is most likely in your changes somewhere. In this case, you will need 
> to add your changes back in until the problem re-appears. Your most 
> recent change is then the likely cause.
>
>    Craig
>
>
> -----------------------------------------------------------------------
>  Craig Southeren          Post Increment – VoIP Consulting and Software
>  craigs postincrement com au                   www.postincrement.com.au
>
>  Phone:  +61 243654666      ICQ: #86852844
>  Fax:    +61 243656905      MSN: craig_southeren hotmail com
>  Mobile: +61 417231046      Jabber: craigs jabber org
>
>  "It takes a man to suffer ignorance and smile.
>   Be yourself, no matter what they say."   Sting