Huge slowdown opening new tabs after opening "Go" menu

RESOLVED EXPIRED

Status

()

Firefox
General
RESOLVED EXPIRED
13 years ago
13 years ago

People

(Reporter: Brad Jackson, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050511 Firefox/1.0+
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050511 Firefox/1.0+

I have noticed that after I click on the "Go" menu on the main window, then
middle click links to open pages in new tabs, Firefox sits for 5+ seconds with
the CPU at 100% before the tab will even appear. As long as I stay away from
that menu, tabs will appear within a second of middle clicking a link.

This is consistently reproducible at, for example, the mozillaZine forums.  If I
middle click the first two Firefox forum links, they open almost instantly. If I
then open the "Go" menu, then middle click the second two Firefox forum links,
it will hammer away, struggling to open the tabs and start rendering the pages.
It's almost acting like it's parsing the entire browser history for each page load.

Note that I am using a Pentium II 450 MHz with 256 MB, so this may not be as
noticible on a P4. I also usually have my history retention set to 21 or 30
days, which may or may not be a factor.

Reproducible: Always

Steps to Reproduce:
1. Open "Go" menu
2. Middle click some links to open new tabs
Actual Results:  
Tabs open and pages render slowly

Expected Results:  
Tab opening and page rendering should operate at normal speed
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/
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
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.