Closed
Bug 297449
Opened 20 years ago
Closed 19 years ago
cannot scroll or find in a URL that Safari has no trouble with
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: jonathan.payne, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 When I load this page my CPU pegs (I have dual 2.5Ghz G5 power mac). Eventually the page is rendered but if I try to scroll the page at all, the CPU again pegs and the page eventually scrolls. If I try to search I am not sure that ever works. I tried the same page in Safari and it works fine. Reproducible: Always Steps to Reproduce: 1. Go to the specified URL 2. Page down one page at a time. 3. Actual Results: The page came up slowly at first and both CPUs were pegged. When I paged down same thing happened. It's unusable. Expected Results: Been nice and smooth and awesome like 99.99% of the pages I have ever visited.
Comment 1•20 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050612 Firefox/1.0+ ID:2005061207 WFM
| Reporter | ||
Comment 2•20 years ago
|
||
And it works for me, now, as well. Maybe because I quit and then restarted Firefox since yesterday? Not sure what to say. If you want to close this bug we can re-open it again later if we can come up with more information about what led up to the problem.
| Reporter | ||
Comment 3•20 years ago
|
||
I am seeing this problem over and over and random web sites. I do not know what is wrong, but firefox gets very slow. I will load a page, short, maybe three screens, simple layout, BOTH CPUs pegged and my CPU fans turn on, and finally the short little page is displayed. BUT, if I quit firefox and restart it and go to the same page, zero problems. Something is wrong. You may need to pay serious attention to this. I's a fairly recent development.
Comment 4•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 5•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•