Closed
Bug 170856
Opened 24 years ago
Closed 16 years ago
Bonsai page takes an eternity to load...
Categories
(SeaMonkey :: Tabbed Browser, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: roland.mainz, Unassigned)
References
()
Details
(Whiteboard: [bugday0420])
Attachments
(1 file)
|
234.72 KB,
application/x-gzip
|
Details |
Trying to load the following Bonsai page takes an eternity to load while Mozilla
is consuming 100% CPU all the time:
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=mozilla%2F&filetype=match&who=&whotype=match&sortby=Date&date=hours&hours=8760&mindate=&maxdate=&cvsroot=%2Fcvsroot
Steps to reproduce:
1. Start Mozilla
2. Cut&paste the example URL into Mozilla
3. Press "enter" and wait for the query response. During that time no CPU is
consumed
4. If query response data are start loading the CPU usage hits 100% while
mozilla becomes more and more unuseable - for the next hour (after that I killed
mozilla) ...
| Reporter | ||
Comment 1•24 years ago
|
||
I forgot the buildid: 2002-09-23-08-trunk on SuSE Linux 6.4 x86 (300MHz)
| Reporter | ||
Comment 3•24 years ago
|
||
Torben wrote:
> Old bug. Is this still a problem?
It's still ugly slow... ;-(
Comment 4•23 years ago
|
||
Nothing really jumps out except the 13 percent of time spent in attribute
parsing.
Comment 5•23 years ago
|
||
>It's still ugly slow... ;-(
true, very true.....
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 6•17 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 7•17 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 8•17 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 9•17 years ago
|
||
Well, the page does not load blazingly fast, but never will eat more than about 30% CPU on my System while loading. And loading the Page took something about ten to fifteen seconds here, thats no eternity.
Have tried with the current SM 2.0b2pre on Windows and an LinuxVM, also SM 1.1.17 with an win2kVM.
I think, this should be closed as wfm now, will do so the next few days exept someone can reproduce this with an current Build.
Ever confirmed: false
Comment 10•17 years ago
|
||
Tobias, your computer is likely on the order of 30-40x faster than the one Roland was using when he filed this bug. So 15s would have been closer to 10 minutes for him; pretty darned close to an eternity. ;)
One relevant question is how fast other browsers (Safari, IE, Chrome, Opera) load that page for you.
Comment 11•17 years ago
|
||
Might be. Now I have tried at home, using an 2002er Athlon XP 1700+, 512 MB RAM, WinXP SP3, and loading the page took about two and a half minutes, consuming mostly something between 25-35% CPU, maximum 70%.
Have tested with:
Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.2pre) Gecko/20090724 SeaMonkey/2.0b2pre
Current IE 8 on WinXP needs also something about 2 1/2 Minutes to load the page, but eats more CPU, most time while loading something between 60-80%, maximum 100%.
I have no older SeaMonkey or Firefox installed, and no other Browser, so I can't do better testing at moment.
Comment 12•16 years ago
|
||
Build identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.9) Gecko/20100317 SeaMonkey/2.0.4
The page loads comparably with Firefox 3.6.3 (Linux), IE8 (Windows), Chrome (Windows) and Safari (Mac). Any further issues here seem like an issue with Bonsai and not Seamonkey.
Resolving WORSKFORME.
Assignee: general → general
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Component: General → JavaScript Engine
Product: SeaMonkey → Core
QA Contact: general → general
Resolution: --- → WORKSFORME
Assignee: general → nobody
Component: JavaScript Engine → Tabbed Browser
Product: Core → SeaMonkey
QA Contact: general → tabbed-browser
You need to log in
before you can comment on or make changes to this bug.
Description
•