Re: [issue1893] Firefox consumes 100% CPU while polling

On Sun, Sep 25, 2011 at 1:26 AM, Francois Tigeot (via DragonFly issue
tracker) <[e-mail]> wrote:
>
> Francois Tigeot <[e-mail]> added the comment:
>
> Seamonkey 2.3.1 also burns 100% cpu. The pattern is a bit different:
>
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 漤oll(0x7fffff7fcbc0,0x9,0x3e7fc18)
> ꀹ73:3 ꀠ澵eamonkey-bin RET ꀠpoll 8
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 淸ettimeofday(0x7fffff7fcdf0,0)
> ꀹ73:3 ꀠ澵eamonkey-bin RET ꀠgettimeofday 0
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 淸ettimeofday(0x7fffff7fcdf0,0)
> ꀹ73:3 ꀠ澵eamonkey-bin RET ꀠgettimeofday 0
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 淸etpeername(0x42,0x7fffff7fcaa0,0x7fffff7fca5c)
> ꀹ73:3 ꀠ澵eamonkey-bin RET ꀠgetpeername -1 errno 57 Socket is not connected
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 淸etpeername(0x44,0x7fffff7fcaa0,0x7fffff7fca5c)
> ꀹ73:3 ꀠ澵eamonkey-bin RET ꀠgetpeername -1 errno 57 Socket is not connected
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 淸etpeername(0x3d,0x7fffff7fcaa0,0x7fffff7fca5c)
> ꀹ73:3 ꀠ澵eamonkey-bin RET ꀠgetpeername -1 errno 57 Socket is not connected
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 淸etpeername(0x38,0x7fffff7fcaa0,0x7fffff7fca5c)
> ꀹ73:3 ꀠ澵eamonkey-bin RET ꀠgetpeername -1 errno 57 Socket is not connected
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 淸etpeername(0x23,0x7fffff7fcaa0,0x7fffff7fca5c)
> ꀹ73:3 ꀠ澵eamonkey-bin RET ꀠgetpeername -1 errno 57 Socket is not connected
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 淸etpeername(0x45,0x7fffff7fcaa0,0x7fffff7fca5c)
> ꀹ73:3 ꀠ澵eamonkey-bin RET ꀠgetpeername -1 errno 57 Socket is not connected
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 淸etpeername(0x43,0x7fffff7fcaa0,0x7fffff7fca5c)
> ꀹ73:3 ꀠ澵eamonkey-bin RET ꀠgetpeername -1 errno 57 Socket is not connected
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 淸etpeername(0x47,0x7fffff7fcaa0,0x7fffff7fca5c)
> ꀹ73:3 ꀠ澵eamonkey-bin RET ꀠgetpeername -1 errno 57 Socket is not connected
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 淸ettimeofday(0x7fffff7fcb60,0)
> ꀹ73:3 ꀠ澵eamonkey-bin RET ꀠgettimeofday 0
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 漤oll(0x7fffff7fcbc0,0x9,0x3e7fc18)
> ꀹ73:3 ꀠ澵eamonkey-bin RET ꀠpoll 8
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 淸ettimeofday(0x7fffff7fcdf0,0)
> ꀹ73:3 ꀠ澵eamonkey-bin RET ꀠgettimeofday 0
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 淸ettimeofday(0x7fffff7fcdf0,0)
> ꀹ73:3 ꀠ澵eamonkey-bin RET ꀠgettimeofday 0
> ꀹ73:3 ꀠ澵eamonkey-bin CALL 淸etpeername(0x42,0x7fffff7fcaa0,0x7fffff7fca5c)
>
> fstat output is available in this file:
> http://leaf.dragonflybsd.org/~ftigeot/fstat_seamonkey.txt

Hmm, could you also post the sockstat for the seamonkey?

Currently it looks like mis-notified "socket is connected" events.

Best Regards,
sephe

-- 
Tomorrow Will Never Die