Closed Bug 153772 Opened 22 years ago Closed 22 years ago

100% cpu use occuring frequently with pipelining enabled

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 146884

People

(Reporter: jmd, Assigned: Matti)

References

Details

(Keywords: perf, qawanted, regression)

Attachments

(1 file)

strace output on pid 1348
117.77 KB, application/x-gzip
Details 
After using the browser component of mozilla for a while, seemingly randomly,
mozilla starts sucking 100% CPU. Here's relevent ps output:

USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
mozilla   1336  0.0  0.5  2044  720 pts/3    S    13:09   0:00 run-mozilla.sh
mozilla   1347  0.0 27.5 60276 34832 pts/3   S    13:09   0:00 mozilla-bin
mozilla   1349  0.0 27.5 60276 34832 pts/3   S    13:09   0:00 mozilla-bin
mozilla   1351  0.0 27.5 60276 34832 pts/3   S    13:09   0:01 mozilla-bin
mozilla   1359  0.0 27.5 60276 34832 pts/3   S    13:11   0:00 mozilla-bin
mozilla   1407  0.0  8.7 217996 11028 pts/3  S    13:47   0:05 java_vm
mozilla   1409  0.0  8.7 217996 11028 pts/3  S    13:47   0:00 java_vm
mozilla   1410  0.0  8.7 217996 11028 pts/3  S    13:47   0:00 java_vm
mozilla   1411  0.0  8.7 217996 11028 pts/3  S    13:47   0:00 java_vm
mozilla   1412  0.0  8.7 217996 11028 pts/3  S    13:47   0:00 java_vm
mozilla   1413  0.0  8.7 217996 11028 pts/3  S    13:47   0:00 java_vm
mozilla   1414  0.0  8.7 217996 11028 pts/3  S    13:47   0:00 java_vm
mozilla   1415  0.0  8.7 217996 11028 pts/3  S    13:47   0:00 java_vm
mozilla   1416  0.0  8.7 217996 11028 pts/3  S    13:47   0:01 java_vm
mozilla   1418  0.0  8.7 217996 11028 pts/3  S    13:47   0:00 java_vm
mozilla   1420  0.0  8.7 217996 11028 pts/3  S    13:47   0:00 java_vm
mozilla   1423  0.0  8.7 217996 11028 pts/3  S    13:47   0:00 java_vm
mozilla   1424  0.0  8.7 217996 11028 pts/3  S    13:47   0:00 java_vm
mozilla   1425  0.0 27.5 60276 34832 pts/3   S    13:47   0:00 mozilla-bin
mozilla   1427  0.0  8.7 217996 11028 pts/3  S    13:47   0:00 java_vm
mozilla   1428  0.0  8.7 217996 11028 pts/3  S    13:47   0:00 java_vm
mozilla   1429  0.0  8.7 217996 11028 pts/3  S    13:47   0:00 java_vm
mozilla   1426  0.0 27.5 60276 34832 pts/3   T    13:47   0:00 mozilla-bin
mozilla   1345  3.5 27.5 60276 34832 pts/3   S    13:09   7:16 mozilla-bin
mozilla   1348 81.4 27.5 60276 34832 pts/3   R    13:09 164:39 mozilla-bin
mozilla   3357  0.0  8.7 217996 11028 pts/3  S    16:31   0:00 java_vm
mozilla   3358  0.0  8.7 217996 11028 pts/3  S    16:31   0:00 java_vm

As you can see, one pid of mozilla, 1348, has used 164 minutes of CPU time.
No tabs are open with running javascript, or animated gifs. I can go sit with
one window and tab open at about:blank, cpu use remains. I'll attach a strace of
that pid. Seems to be waiting for something... constant gettimeofday()'s, with a
poll() on fd 7.

This is happened to me every day for a while now. Only cure to drop CPU back
down is restarting mozilla.
27150 gettimeofday's in 5.16 seconds.
Mozilla zombified on exit that run:

mozilla   1336  0.0  0.5  2044  720 pts/3    S    13:09   0:00 run-mozilla.sh
mozilla   1347  0.0 28.0 49304 35368 pts/3   S    13:09   0:00 mozilla-bin
mozilla   1407  0.0  8.6 217996 10936 pts/3  S    13:47   0:05 java_vm
mozilla   1409  0.0  8.6 217996 10936 pts/3  S    13:47   0:00 java_vm
mozilla   1410  0.0  8.6 217996 10936 pts/3  S    13:47   0:00 java_vm
mozilla   1411  0.0  8.6 217996 10936 pts/3  S    13:47   0:00 java_vm
mozilla   1412  0.0  8.6 217996 10936 pts/3  S    13:47   0:00 java_vm
mozilla   1413  0.0  8.6 217996 10936 pts/3  S    13:47   0:00 java_vm
mozilla   1414  0.0  8.6 217996 10936 pts/3  S    13:47   0:00 java_vm
mozilla   1415  0.0  8.6 217996 10936 pts/3  S    13:47   0:00 java_vm
mozilla   1416  0.0  8.6 217996 10936 pts/3  S    13:47   0:01 java_vm
mozilla   1418  0.0  8.6 217996 10936 pts/3  S    13:47   0:00 java_vm
mozilla   1420  0.0  8.6 217996 10936 pts/3  S    13:47   0:00 java_vm
mozilla   1423  0.0  8.6 217996 10936 pts/3  S    13:47   0:00 java_vm
mozilla   1424  0.0  8.6 217996 10936 pts/3  S    13:47   0:00 java_vm
mozilla   1425  0.0  0.0     0    0 pts/3    Z    13:47   0:00 mozilla-bin <defunct>
mozilla   1427  0.0  8.6 217996 10936 pts/3  S    13:47   0:00 java_vm
mozilla   1428  0.0  8.6 217996 10936 pts/3  S    13:47   0:00 java_vm
mozilla   1429  0.0  8.6 217996 10936 pts/3  S    13:47   0:00 java_vm
mozilla   1426  0.0 28.0 49304 35368 pts/3   T    13:47   0:00 mozilla-bin
mozilla   3753  0.0  8.6 217996 10936 pts/3  S    17:19   0:00 java_vm
mozilla   3754  0.0  8.6 217996 10936 pts/3  S    17:19   0:00 java_vm
mozilla   1345  3.4 28.0 49304 35368 pts/3   S    13:09   8:45 mozilla-bin


1345 still using 3.4% cpu but strace on it showed nothing happening.
Keywords: qawanted
ps is probably giving you a cumulative CPU usage... if there is a plugin or
something (I notice all the java_vm, although they're in separate threads, so I
don't think they should affect mozilla-bin's numbers) on a page you have loaded,
it might easily take 100% of the CPU.  If it was there 80% of the time, you will
get ps showing 80% CPU.

What do you get from top?  That should give you real-time usage numbers.

27150 gettimeofday's in 5.16 seconds does seem like a lot...
No, no plugins were running. Top shows 100% CPU use, like I said. The other 20%
is system use, attending to mozilla.
  PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
 2150 mozilla   14   0 45576  39M 32364 R    97.0 32.3  31:49 mozilla-bin

java was already running this time too, but I hadn't had an applet running for
hours before the spontaneous 100% started happening. I'll disable java
completely and see if this happens tomarrow.
Lately (within the past week or so) I've been noticing that mozilla would go to
100% CPU during normal usage too.   I can't seem to quite place exactly what is
triggering it.

I'll often have a browser window with 10 or so tabs open, MailNews, and
Chatzilla.   I can close up the Browser windows and MailNews, so just chatzilla
is open and it will still be using all available CPU time.   Closing up the last
remaining component will allow mozilla to terminate normally and CPU usage goes
back to normal.

Note: Mozilla and my pc (win2k) are still usable during this time.  Mozilla just
acts a bit lagged. 
I've been seeing this for several weeks, also.  It just happened to me after
maybe 15 minutes of use (which is typical).     I don't have any plugins or java
loaded; it all seems like regular pages in three windows.  As others have said,
once it happens, the only way to stop it is exiting; it seems to be a lot of
repeated poll and gettimeofday calls.

I'm using a RedHat rawhide version at the moment (Mozilla/5.0 (X11; U; Linux
i686; en-US; rv:1.0.1) Gecko/20020625), but I've been seeing it with nightlies,
too.  It doesn't seem to happen with 1.1alpha.
It's pretty frustrating!

Seeing exactly the same as in comment #6 - using win-xp pro.
Severity: normal → major
Keywords: perf, regression
As mentioned in #mozillazine, maybe some relation to bug 146884? 

Reporter: Do you have pipelining enabled? 
(I do and I experience this bug, fwiw)
Happens to me a lot lately on W2K using nightlies.
Now testing 2002070310.

I have also noticed that Moz lately consumes 100% for about 3 seconds on exit
and when closing the last open window while using QuickLaunch. Is this related
to this bug?
Yes, pipelining and keepalive are enabled. Haven't seen this since I disabled
Java though.
I am also seeing this on WinXP, 2002070508. The browser starts to use 100% cpu
after browsing for a while. Browsing is still completely functional and there is
no hang. I turned pipelining off and that has stopped it happening.
Pipelining seems to be the common thread here.
My comment #6 should include that I too had pipelining enabled.
OS: Linux → All
Summary: 100% cpu use occuring frequently → 100% cpu use occuring frequently with pipelining enabled
confirming.
I have Pipelining enabled as well
Isn't pipelining enabled by default? Seems an odd choice for the cause of this.
Just to clarify my situtation at least, I was seeing this usually every day
after say 4-8 hours of browser use. 10 days ago I disabled Java and haven't seen
it once since. I haven't done quite as much surfing this week, but certainly 4-8
hours total. I'll post again ASAP if it should happen again with Java still off.
I turned off HTTP pipelining yesterday and haven't had this problem since then.
 It used to happen about once every 10 minutes.

*** This bug has been marked as a duplicate of 146884 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
OK, I'll verify. Finally happened to me with Java still off. Held down ^R for a
while and boom.
Status: RESOLVED → VERIFIED
*** Bug 156340 has been marked as a duplicate of this bug. ***
Breaking the circular duplicates -> reopening.
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
I don't see any circular duplicates...

*** This bug has been marked as a duplicate of 146884 ***
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
Noticed the same problem. . .friend was running a webcam that uses java and the
problem seemed to go away when he switched to using javascript.  Had/have
pipelining enabled.  I'm a fairly repetative user; I do pretty much the same
things to my Mozilla every day, in usually the same order.  I will report back
if I have the problem again (he switched to Javascript about a week+ ago).
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: