o Laurent Schweizer [06/03/08 10:22]: > Hello, > > Attached log of my last test with last version. > > I wait after the last call before killing sems . > > Laurent > something must be wrong with your application logic: you still have 74 sessions running. check that you end all sessions with setStopped().
Stefan > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Sayer > Sent: lundi 2 juin 2008 13:31 > To: Raphael Coeffic > Cc: [EMAIL PROTECTED] > Subject: Re: [Semsdev] 2 problems with sems > > > > o Raphael Coeffic [06/02/08 12:26]: >>>> It looks like you have a lot (405) of thrashed sessions still in > memory. >>> where do you see them? >>> >> In the memory traces. > ah ;) > > but how is the transactions on sip stack level linked to the session > objects other than the transaction id? i mean, how will freeing the > session affect sip stack's memory? > > i see the count 405 only in loss record 43, 47 and 106, and they are all > > sip transaction related and not on dialog/session level. > > Stefan > >> -Raphael. > -- Stefan Sayer VoIP Services [EMAIL PROTECTED] www.iptego.com iptego GmbH Am Borsigturm 40 13507 Berlin Germany Amtsgericht Charlottenburg, HRB 101010 Geschaeftsfuehrer: Alexander Hoffmann _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
