Bug#714920: ekiga: slow startup

[mazzeppanell]

> Try using ekiga -d 8 and see if some intermediate lines are written
> during inactivity.
>
Yes, i attach the output of "ekiga -d 8" from the beginning to the point 
in which the main window appears.

In particular we can see in the void time gaps obtained with '-d 3' switch:

< ... >
2013/07/04 12:59:32.347	  0:02.201	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:33.347	  0:03.202	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:34.348	  0:04.202	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:35.348	  0:05.202	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:36.348	  0:06.203	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:37.348	  0:07.203	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:38.349	  0:08.203	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:39.349	  0:09.204	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:40.350	  0:10.204	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:40.530	  0:10.385	 Housekeeper:0xadeedb40	Ekiga	Stopped 
STUN detector
2013/07/04 12:59:40.530	  0:10.385	 Housekeeper:0xadeedb40	PTLib 
Destroyed thread 0x89cdb00 StunDetector:0xada7db40(id = 0)
2013/07/04 12:59:40.530	  0:10.385	 Housekeeper:0xadeedb40	PTLib 
MONITOR: timers=1, expiries=2
2013/07/04 12:59:40.530	  0:10.385	 Housekeeper:0xadeedb40	SIP	NAT 
Binding refresh started.
2013/07/04 12:59:40.531	  0:10.385	 Housekeeper:0xadeedb40	SIP	NAT 
Binding refresh finished.
2013/07/04 12:59:40.531	  0:10.385	 Housekeeper:0xadeedb40	PTLib 
MONITOR: timers=1, expiries=2
2013/07/04 12:59:41.350	  0:11.204	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:42.350	  0:12.205	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:43.351	  0:13.205	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:44.351	  0:14.205	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:45.351	  0:15.206	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:45.444	  0:15.299	Network In...0xadc7db40	PWLib	File 
handle low water mark set: 39 PUDPSocket
2013/07/04 12:59:45.444	  0:15.299	Network In...0xadc7db40	PWLib	Closing 
channel, fd=39
2013/07/04 12:59:46.352	  0:16.206	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:47.352	  0:17.207	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:48.352	  0:18.207	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:49.353	  0:19.207	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:50.353	  0:20.208	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:50.531	  0:20.385	 Housekeeper:0xadeedb40	PTLib 
MONITOR: timers=1, expiries=2
2013/07/04 12:59:50.531	  0:20.385	 Housekeeper:0xadeedb40	SIP	NAT 
Binding refresh started.
2013/07/04 12:59:50.531	  0:20.386	 Housekeeper:0xadeedb40	SIP	NAT 
Binding refresh finished.
2013/07/04 12:59:51.354	  0:21.208	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:52.354	  0:22.209	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:53.355	  0:23.209	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:54.355	  0:24.209	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
2013/07/04 12:59:55.355	  0:25.210	Opal Garbage:0xadcbeb40	SIP	Garbage 
collection: transactions=0, connections=0
< And here it shows up >
< ... >

One garbage collection per second... but this activity happens regularly 
during program execution.
>
> This is not normal. It does not appear here. This sometimes appear when
> there are some issues with the DNS and the STUN result, but as written
> below the STUN is not the case. I suppose you have restarted ekiga after
> disabling network detection, right?
>
Sure :)
>
> Another idea is to look with wireshark at second 10 and 25 what packets
> you receive. If it is DNS response, then it would confirm my hypothesis
> about DNS exchange taking so long. Alternatively, you can try another
> DNS server (in /etc/resolv.conf), e.g. someone wrote on our mailing list:
>
> "I had a similar problem with dns servers where the isp provider didn't
> have a good dns server and I had many delays on the connections.
>
> I use the dns from opendns.com and I have no problem anymore..."
>
No improvements changing DNS server.

Thanks for support.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ekiga-d8
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20130704/46cc99a9/attachment-0001.ksh>