Opening a new Navigator Window when your home page contains a Java app locks up Mozilla

RESOLVED INCOMPLETE

Status

Core Graveyard
Java: OJI
RESOLVED INCOMPLETE
14 years ago
5 years ago

People

(Reporter: Graham Menhennitt, Assigned: Kyle Yuan)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122

This bug appeared between 1.8a4 and 1.8a5.

If your home page contains a Java app and you do File->New->Navigator Window, it
loads the Home Page (even if you have preferences set to start with a blank
page!). If you then close the new window, the old window is essentially dead.
You can close it but that's about all. If you do close it, the mozilla process
does not exit - you need to use Task manager to kill it. I don't know if it is
relevant, but I have Optimoz Mouse Gestures 1.0 installed.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Updated

14 years ago
Summary: Opening a new Navigator Window when your home page conatins a Java app locks up Mozilla → Opening a new Navigator Window when your home page contains a Java app locks up Mozilla
Version: unspecified → Trunk
WFM Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050404

Graham, is this a problem with a current build/release? If so, can you post a
URL where this happend.
(Reporter)

Comment 2

13 years ago
Carsten,

Yes, it still happens with 1.8b (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.8b) Gecko/20050217). I have my home page set to our local intranet that you
won't have access to. I'll try to find something else that does it, hang on...
... ok, try http://java.sun.com/applets/other/ImageLoop/index.html as your home
page and set the preference to open your home page when opening a new navigator
window. Open Mozilla, open a new navigator window, close the new window, the old
window will now be dead. I suspect it's waiting for the other window to finish
closing. My Java version is "Version 1.5.0 (build 1.5.0-b64)" but it used to
happen with 1.4 also.
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/
(Reporter)

Comment 4

13 years ago
This appears to be fixed in Firefox 1.0.7.
(Reporter)

Comment 5

13 years ago
Looks like I spoke too soon - it just happened again. It didn't happen yesterday
when I tested it, so it isn't 100% reproducable.

Since I reported the original bug, I have set my home page to 'about:blank' to
avoid the problem. Yesterday, to test it, I set it to the java.sun.com link
below. I left it like that and today the bug occurred when I opened a new
window. This is with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
Gecko/20050915 Firefox/1.0.7. The original window is not quite dead (as I
previously said it was), you can switch tabs and close tabs. But nothing happens
if you click on a hyperlink, you can't open menus (File, Edit, etc.), and mouse
gestures don't respond.

I paused it a few times using VC++ and got a couple of different stack
backtraces (without symbols unfortunately):
>	ntdll.dll!7c90eb94() 	
 	user32.dll!77d49418() 	
 	awt.dll!6d0e3e00() 	
 	awt.dll!6d0e3c0d() 	
 	awt.dll!6d0e4bbe() 	
 	jvm.dll!6d6c168d() 	
 	jvm.dll!6d714179() 	
 	jvm.dll!6d6c155e() 	
 	jvm.dll!6d6c1282() 	
 	jvm.dll!6d6c12bb() 	
 	ntdll.dll!7c90e21f() 	
 	jvm.dll!6d6dbbe9() 	
 	jvm.dll!6d73e77f() 	
 	jvm.dll!6d73e74d() 	
 	jvm.dll!6d711e59() 	
 	ntdll.dll!7c918dfa() 	
 	ntdll.dll!7c90d625() 	
 	ntdll.dll!7c90eacf() 	
and another time
>	ntdll.dll!7c90eb94() 	
 	ntdll.dll!7c90e9ab() 	
 	kernel32.dll!7c8094f2() 	
 	user32.dll!77d4989a() 	
 	kernel32.dll!7c8399f3() 	
 	user32.dll!77d495f9() 	
 	user32.dll!77d4c96c() 	
 	user32.dll!77d496a8() 	
 	jpinscp.dll!6d422b7b() 	
 	jpinscp.dll!6d422629() 	
 	jpioji.dll!6d443688() 	
 	firefox.exe!0053cc01() 	
 	firefox.exe!0053c874() 	
 	firefox.exe!006496bb() 	
 	firefox.exe!006480bb() 	
 	gdi32.dll!77f1b230() 	
 	gdi32.dll!77f1adfc() 	
 	gdi32.dll!77f1c32a() 	
 	gdi32.dll!77f307f8() 	
 	firefox.exe!00650073() 	
 	firefox.exe!006b1d15() 	
 	firefox.exe!0054ed48() 	
 	firefox.exe!00605d73() 	
 	firefox.exe!0054e5a5() 	
 	firefox.exe!0067e03f() 	
 	firefox.exe!0067e0f6() 	
 	firefox.exe!00553627() 	
 	firefox.exe!005f1872() 	
 	firefox.exe!0067d58f() 	
 	firefox.exe!00582c67() 	
 	xpcom.dll!6030d258() 	
 	firefox.exe!00687a08() 	
 	firefox.exe!0067e1f8() 	
 	firefox.exe!006d1d3c() 

Comment 6

13 years ago
looks like Java is hanging, not Mozilla.

==> OJI
Assignee: general → yuanyi21
Component: General → Java: OJI
Product: Mozilla Application Suite → Core
QA Contact: general → pete.zha

Updated

8 years ago
Component: Java: OJI → Java: OJI
Product: Core → Core Graveyard

Comment 7

5 years ago
Mass-closing bugs in the "OJI" component: OJI plugin integration was replaced with npruntime long ago, and these bugs appear to be irrelevant now. If there is in fact a real bug that remains, please file it new in the "Core" product, component "Plug-ins".
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.