Opening tabs causes Mozilla 1.7A4 to crash

RESOLVED EXPIRED

Status

SeaMonkey
General
--
critical
RESOLVED EXPIRED
13 years ago
12 years ago

People

(Reporter: David K, Unassigned)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a4) Gecko/20040927
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a4) Gecko/20040927

Here are the detailed steps to reproduce the problem I am having.  I've tried it
twice and received the same results both times.  

1. Uninstall Mozilla 1.7A2, don't delete the directory
2. Install Mozilla 1.7A4 (regular install, staying in memory)
3. Go to:  http://www.gamefaqs.com/console/ps2/game/28525.html
4. On this page right click on the 'message boards' link and choose 'open in a
new window'
5. Go to the message boards tab
6. Choose a message and right-click open in a new tab
7. Go to this message tab
8. Right click on the tab header.  It reads 'GameFAQs: General Message List'. 
Observe that the menu doesn't appear or takes a long time to appear
9. Right click on any link.  Observe that the menu doesn't appear or takes a
long time to appear.
10.  Try to drag the mozilla window/app to a new location.  It fails.  Mozilla
has basically froze
11. Close Mozilla with Ctrl-Alt-Delete

And finally:

12.  Do the same without opening the links in new windows.  Observe Mozilla
1.7A4 works fine

Reproducible: Always
Steps to Reproduce:
See the details section above.

Actual Results:  
Mozilla crashed when the steps were done using tabs.  It was fine if tabs
weren't used.

Expected Results:  
It looks like opening tabs causes Mozilla 1.7A4 to crash.  Obviously that
shouldn't happen.
(Reporter)

Updated

13 years ago
Component: Tabbed Browser → Browser-General
Product: Browser → Seamonkey
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: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.