Closed
Bug 256248
Opened 21 years ago
Closed 21 years ago
near 100% CPU load while viewing this page
Categories
(SeaMonkey :: General, defect)
SeaMonkey
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: relf, Unassigned)
References
()
Details
(Keywords: perf)
Linux build 2004080905
The provided URL makes Mozilla eat almost 100% CPU.
That's odd since the incrementing counters do not seem to be a big deal for
1.67GHz CPU.
I've tried Konqueror and it makes as twice as less CPU load showing that page.
Comment 1•21 years ago
|
||
70% on amd64 3000
Same problems on Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7)
Gecko/20040803 Firefox/0.9.3 running on W2K Prof SP4, Athlon XP 1700+.
IE on this page has much lower CPU usage.
I also got 100% CPU load on my sytem , but also in IE ,so my guess is that its
not a FF only 'bug'.
(AMD pro 1300+ - Geforce4MX 440 - 384 MB SDRAM - Onboard LAN[SIS 900])
(Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803
Firefox/0.9.3)
Comment 4•21 years ago
|
||
I got it up to 31% CPU for this build:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040820
Firefox/0.9.1+
WinXP Pentium4 3GHz 512M RAM
Comment 5•21 years ago
|
||
About 20% of the total time is spent under jsd_FunctionCallHook and
jsd_ObjectHook combined.
For the rest, the page has an incredibly inefficient algorithm for converting
numbers to the strings it shows in the textboxes, and it tries to run said
algorithm 43,000 times a second (43 counters and 1ms timeout). This in addition
to the fact that it tries to set values of textboxes 43000 times a second...
I suppose we could try to optimize the "foo.value = foo.value" case (which this
page hits a lot), but that would slow down value setting in general. Doesn't
seem worth it.
In any case, there is no actual performance problem here (as in, not keeping up
with what the page wants). So...
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•