Bug 245202 (FrozenNewWindow)

When a new browser window in v1.7 create, it appears to be frozen.

RESOLVED EXPIRED

Status

--
major
RESOLVED EXPIRED
15 years ago
13 years ago

People

(Reporter: BenjaminHui01, Unassigned)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040514
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040514

I have Win2K. running on Mozilla v1.7.  However, when I clicked on a link in the
URL above, like clicking on the picture of the page, a new window is created. 
But the new window does not respond, it appears to be frozen.  On closer
inspection in the task manager window, it is listed as running.  When I go back
to the original URL above and tried to click on another picture, a new windows
is again created and the same thing happens.  But each new window is reported as
running, even though they are obvious not responding.

Reproducible: Always
Steps to Reproduce:
1.http://www.newegg.com/app/viewProductDesc.asp?description=13-128-241&catalog=23&manufactory=BROWSE
2.click on any picture of the motherboard
3.a new window is created and it does not respond at all

Actual Results:  
New window does not respond

Expected Results:  
I should be able to browse as usual, but window is in  frozen state.

I have the browser extension installed, but I don't suppose this would cause the
problem, since I have been using the tab extension since v1.5
(Reporter)

Updated

15 years ago
Alias: FrozenNewWindow
(Reporter)

Comment 1

15 years ago
Additionally, when I tried to terminate anyone of the new windows through Task 
Manager, all instances of Mozilla is terminated including the original Mozilla 
instance that spawned the new windows.  Thanks.

Ben
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: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.