2002012103 pegs CPU in different way that builds earlier this week

RESOLVED WORKSFORME

Status

SeaMonkey
General
RESOLVED WORKSFORME
16 years ago
13 years ago

People

(Reporter: Steve Peterson, Assigned: asa)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
2002012103 on Win2K SP2.  Thinkpad T21 with 850MHz / 384 MB.

I'm seeing two different new CPU usage related behaviors on the specified build
that seem related.

The first is that the browser occasionally pegs the CPU for 3-4 seconds every
couple minutes when it does not have the focus.  There isn't a specific page
that causes this problem that I've been able to deted.

The second is that, if left idle, the browser eventually pegs the CPU and must
be killed.  This is similar to the "eating memory when idle" bug but its CPU
this time.

Both of these behaviors are new to me in the named build over something 4-5 days
older.

Sorry that I don't have more specifics on pages, but thought I would report this
as the behavior started when I installed this build.
(Assignee)

Comment 1

16 years ago
Without specific steps to reproduce there isn't much that can be done with this
report.
(Assignee)

Comment 2

16 years ago
Please reopen if you can provide specific steps that cause the CPU spike and you
can reproduce in a current (0.9.8 or more recent) build. Thanks.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.