Closed
Bug 71668
Opened 24 years ago
Closed 8 years ago
page loading performance issues
Categories
(Core Graveyard :: Tracking, defect)
Core Graveyard
Tracking
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
Future
People
(Reporter: cathleennscp, Unassigned)
References
(Depends on 12 open bugs)
Details
(Keywords: meta, perf)
No description provided.
tracking page loading performance related issues
Updated•24 years ago
|
Comment 3•24 years ago
|
||
agreed
Comment 5•23 years ago
|
||
see comment in bug 96633 - cpu usage 100% and making mozilla quite unusable.
Comment 6•23 years ago
|
||
2002-2-21-03 w2k, probably bug 122996, also bug 98252 (in 0.9.8) has contributed to tiling and fixing several problems with scrolling. not seeing any slow scrolling anymore on many bugs. Please confirm dependencies of this bug, Thanks.
moving tracking/meta bugs out of milestone pools.
Target Milestone: mozilla1.0 → Future
Adding bug 109050: UI freezes for a few seconds loading pages on RedHat.com (appears to also present at http://cnnfn.com http://www.nwa.com and http://www.ussoccer.com, among others). IMO, it's worst at cnnfn. I think it's a very annoying page loading perf issue, but if it's out of place here, feel free to remove.
Depends on: 109050
Comment 9•22 years ago
|
||
Adding bug 143046 - causing various perf problems (see in depending bugs).
Depends on: slowGIF
Comment 10•22 years ago
|
||
Loading page takes nearly 2-5secs in an 233Mhz PC which has 256 MB RAM support. The O.S used is Linux 7.2. Is there any solution for this. If yes, Please suggest.
Comment 11•22 years ago
|
||
Nagarajan, this is a meta bug, not a support forum. Suggesting to find an appropriate testcase (i.e. a page that exhibits the slow load problem), ruling out any bandwidth restriction. If testcase page loading is still slower than on any other browser on the same machine/OS combination, then check the bugs depended on this one (see list above). If none of them seems related, please file a new bug.
Comment 12•21 years ago
|
||
Here is another testcase to reproduce this problem easily in netscape 7/mozilla browser on solaris/win2k/linux. (This problem is appearing even without the animated gifs) 1. Goto this site: http://sandesh.vsnl.com 2. Login with userid: reddy password: reddy 3. Create a new html file in your harddisk like this: <html> <script> function close() { alert('Loaded') } </script> <frameset col=* row=* onload="close()"> <frame src="http://sandesh.vsnl.com/en/mail.html? sid=I/HutbYs9/4&lang=en&cert=false"> </frameset> </html> 4. Replace the src value of the above html with the new url you got in step 2. 5. Open the html file created in steps 3&4 in netscape/mozilla browser, notice that throbber keep looping and it goes for ever. Status bar shows that "Transferring data from sandesh.vsnl.com..." for ever. 6. Now, instead of keeping the above url inside the frame do it like this: <html> <script> window.location="http://sandesh.vsnl.com/en/mail.html? sid=I/HutbYs9/4&lang=en&cert=false" </script> </html> Note that: the window.location value should be replaced with the new URL generated in step 2 (after login) 7. Open the html edited in step 6 in netscape/mozilla browser.The problem is NOT reproducable. Note: If we open the above said url inside the frame then throbber goes for infinite loop but if we open as said in step 6 this problem will not appear.
Comment 13•21 years ago
|
||
sorry if I spam, but i have had quite a few problems with pages where <script> was used i/o <script type="text/javascript">. It was like that in Firebird, and still is.
Comment 14•21 years ago
|
||
Tricks is a TRACKING bug! Please file a new bug about any specific problems.
Comment 15•13 years ago
|
||
Maybe some of the bugs tracked are relevant for Snappy.
Whiteboard: [Snappy]
Comment 17•13 years ago
|
||
Everything other than dns is too old to be useful
Assignee: taras.mozilla → nobody
Whiteboard: [Snappy]
Updated•11 years ago
|
Comment 18•8 years ago
|
||
This bug is not being used to track/prioritize engineering work, so I'm going to close it to make that clear. Bugs filed in individual bugzilla components are still prioritized by those teams.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Comment 19•8 years ago
|
||
(In reply to Benjamin Smedberg [:bsmedberg] from comment #18) > This bug is not being used to track/prioritize engineering work, so I'm > going to close it to make that clear. Bugs filed in individual bugzilla > components are still prioritized by those teams. That's too bad, as this is a nice catch-all to see where things are at. Hopefully, they will at least add the "perf" keyword to those other bugs, to provide a way to watch performance overall trends.
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•