Closed Bug 277219 Opened 20 years ago Closed 19 years ago

opening new tab and clicking "home" icon crashes firefox

Categories

(Firefox :: Tabbed Browser, defect)

1.0 Branch
x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: jzwolak, Assigned: bugs)

Details

(Keywords: crash)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0

When viewing a web page that sets the icon in the address bar (say newegg.com or
mozilla.org), Firefox crashes when opening a new tab and clicking on the "home"
icon before the "blank page" turns from gray to white.  Perhaps my slow system
(650 megahertz Athlon) makes the problem possible, where a faster system won't
display a new tab with a gray screen for 0.5-1.0 seconds (like my computer
does).  I have to be quick to reproduce this, but I can do it 100% of the time.

My home icon brings me to http://www.google.com

Reproducible: Always

Steps to Reproduce:
1. start firefox
2. go to http://newegg.com
3. press ctrl-t (for a new tab)
4. quickly after the new tab appears, but before it turns from gray to white,
click on the home icon.
5. wait for a second and Firefox will crash (process will terminate, window
disappears).

Actual Results:  
Firefox's processes terminated and the window disappeared.

Expected Results:  
I expected http://www.google.com to load in my newly created tab.

This version of firefox was installed through Fedora Core 3's packaging system
using a command like "apt-get install firefox".  My architecture is i686 and I
have i686 binaries.
Version: unspecified → 1.0 Branch
WFM in Novell Linux Desktop with Firefox 1.0
Please provide a stacktrace or a talkback id and also try to see if this is
fixed in trunk builds.
Keywords: crash
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
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.