66122 - processor usage huge

Status: VERIFIED INVALID

(SeaMonkey :: General, defect)

Description

[Pekka Sarnila]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.17 i686; en-US; 0.7) Gecko/20010120
BuildID:    own build from 0.7 source (no options)

When just moving mouse over mozilla (in any mode or any page) it
takes about 50% of precessor time (800MHz AMD) (In Netscape 4.75 it
is less than 4%). So there is something seriously wrong in the system
level.

Reproducible: Always
Steps to Reproduce:
1. start mozilla and top
2. move mouse over mozilla and watch CPU user prosentage

Actual Results:  it shows nerly 50%

Expected Results:  in netscape 4.75 less tham 4%

Even when you do absolutely nothing, one process (the main process I
guess) is looping over poll that returns immediatly (look by strace).
I guess the poll should sleep until there is an event (like mouse
move).

Comment 1

[James Green]

Works ok here with my own build from the tip on Linux.

Reporter: can you be more specific? Is this occurring on any specific web pages?
Is it only in the browser (what about mail/news)? My CPU usage somes barely
registers when I hover.

Comment 2

[Håkan Waara]

Adding perf keyword.

Comment 3

[xk]

I notice larger CPU spikes when moving the mouse between the rendering window
space and the URL bar. But moving to/from the throbber, it's nearly neglible.

Comment 4

[James Green]

xk: that shows up as up to 10-15% cpu usage here.

Reporter: I'm missing the obvious. You're compiling with no options which means
you are building a debug, non-optimised build. Try --disable-debug and
--enable-optimize for a start. Read the Unix Build Configurator at
http://webtools.mozilla.org/build/config.cgi to create a .mozconfig file.

Comment 5

[James Green]

Via email:

From: <[e-mail]>
Ok, thanks for that. I'll try it and tell you what happened. But could
you tell me where the debug was going so that I could delete it from
taking disk space.

**Please ensure that ALL messages are entered via bugzilla. Thanks.

The solution to your problem is to 'make -f client.mk clean' then rebuild with
the wanted options.

Comment 6

[Asa Dotzler [:asa]]

without more detailed information this bug is not going to be useful to
developers.  That we are CPU intensive is a known issue.  

Comment 7

[Doron Rosenberg (IBM)]

yeah, best rebuild, maybe even try a new profile as well.

I self build on linux too and never saw it that bad.