303447 - Significant cpu loading with latest nightly build, much more so than Aug 1 build.

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[Chuck Wade]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050803 SeaMonkey/1.0a
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050803 SeaMonkey/1.0a

SeaMonkey is using every spare cycle of my processor (G4, 550MHz). This problem
is new with today's "latest release." I have started and stopped SeaMonkey, with
no change in behavior. Everything appears to be working normally. The problem
does not relate to which window or component is open, and appears even when all
windows are closed. This version is not usable, although I have had it running
for several hours today, but with greatly reduced system performance.

Reproducible: Always

Steps to Reproduce:
1. Start the application
2.
3.

Actual Results:  
Apple's Activity Monitor reports "seamonkey-bin" consistently consuming from 70%
to 90% of the CPU. There are 6 threads and RPRVT is 110.89 MB and Virtual Memory
is 270.15 MB.

Expected Results:  
CPU utilization in the 1 - 3% range when the application is idle. This is normal
behaviour on my system.

Using the default theme.

Comment 1

[Chuck Wade]

I have some additional information on this problem. First, I discovered that,
after letting the SeaMonkey 20050803 build run for several hours, I was able to
quit the application, and re-launch it without it hogging most of the CPU
cycles. In other words, when I first encountered the problem, quitting and
relaunching did not help. I then let SeaMonkey run for several hours (around 4).
While it never stopped sucking up every available cycle, it did stop after
quitting/relaunch.

Note, I did not change anything else on my Mac OS 10.3.9 system, nor did I reboot.

I have also not encountered this problem again with the 20050805 and 20050807
builds. If SeaMonkey was actually doing anything with all those CPU cycles, it
was nothing obvious.

Comment 2

[Andrew Schultz]

Have you seen this problem again?

Comment 3

[Boris Zbarsky [:bzbarsky]]

Is this still an issue?

Comment 4

[Chuck Wade]

As indicated in my 2005-08-08 update, this problem did sort of resolve itself. In subsequent releases of SeaMonkey, I did not directly encounter this problem. However, I continue to this day to have a problem with both SeaMonkey and Thunderbird, where the application will at some point start sucking up all available CPU cycles until quit and restarted. This condition usually occurs after a few hours of operation, but can take up to a day or two to occur. I have never been able to correlate this with anything in particular, and it occurs with the latest version of Mac OS X 10.4.8. I mostly use Thunderbird these days, so I have less operating experience with SeaMonkey. However, I did have this same problem with SeaMonkey up until earlier this year, when I switched to Thunderbird, and noticed the two applications had the same problem. I can't speak directly to the latest version of SeaMonkey.