On 11/18/05, Dâniel Fraga <[EMAIL PROTECTED]> wrote:
> In article <[EMAIL PROTECTED]>,
>         [EMAIL PROTECTED] (Dâniel Fraga) writes:
> >   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
> >  2586 fraga     18   0  109m  12m 9548 S 98.8  9.9   1:04.83 licq
> >       I upgraded from Licq CVS 20051114 to 20051117 and now it uses too
> > much CPU (full load) all the time. Something wrong? Does somebody
> > noticed this too? Thanks.
>
>         I think this problem is related to the patch that shows MSN
> pictures when we pass the mouse over the nickname. If I do this when
> Licq is starting, licq will consume all the cpu forever (even when
> the process is sleeping as above).

I see this CPU loop after resuming from suspend or when someone
changes to online status.  A strace on the looping process shows
"futex(0x8145a24,
FUTEX_WAIT, 1, NULL <unfinished ...>".

Message log:
20:05:05: [MSN] Kristian Heim changed status (NLN).
20:05:06: [MSN] [EMAIL PROTECTED] joined the conversation.
20:05:06: [MSN] Display Picture: Ack received
20:05:06: [MSN] Display Picture: Session Id received (185623953)
20:05:06: [MSN] Display Picture: Got data start message (185623953)
20:05:06: [MSN] Display Picture: Expecting file of size 23512 (Id: 185623953).
20:05:08: [MSN] Display Picture: Successfully completed
(/home/christbw/.licq/users/[EMAIL PROTECTED]).
20:06:56: [MSN] Ping timeout. Reconnecting...
20:06:56: [MSN] Server found at 65.54.239.210:1863.
20:06:57: [MSN] Server found at 207.46.6.45:1863.
20:06:58: [MSN] Authenticating to 65.54.179.192:443

--
Christian


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id845&op=click
_______________________________________________
Licq-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/licq-devel

Reply via email to