Closed
Bug 251031
Opened 20 years ago
Closed 20 years ago
Java locks up Mozilla if Sun Java Plugin can't download Applet
Categories
(Core Graveyard :: Java: OJI, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: richard.perrott, Assigned: yuanyi21)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 MultiZilla/1.6.3.0e
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 MultiZilla/1.6.3.0e
Mozilla locks up if you open a web page contains an Applet and the Sun Java
plugin 1.4.2_04 cannot download e.g. due to server overload etc, the issue can
also occur if Java plugin is configured to use a dead proxy server/port.
Reproducible: Always
Steps to Reproduce:
1. Set (manual) proxy details in Sun Java plugin 1.4.2_04 to point at a live
server, with proxy disabled.
2. Start Mozilla open http://www.excelsior-usa.com/home.html
3. Wait for page to render, as far as it can get, that is!
Actual Results:
All Browser windows and the Java console window are locked.
Expected Results:
Mozilla should instead say the Java class/jar cannot be downloaded, not lock up
any windows (even when requesting/downloading the Java files) and allow normal
use afterwards as failed download.
I suspect that the Java plugin is running in the same thread as a critical
thread, so cannot be culled if it locks for any reason.
Unknown
Comment 1•20 years ago
|
||
wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a2) Gecko/20040711
Sun Java\jre1.5.0\bin\NPJava32.dll that is 1.5 beta 2 build 51
Applet top-right (above NEWS) didn´t load, got an error message in the status
bar. When I clicked on the applet, I could start the Java console, that gave me
a lot of info, starting with that class missing:
com.diginet.groopz.suite.ec.applet.GroopzApplet.class
I don´t use a proxy, so I didn´t configure anything, just clicked on your link.
http://www.excelsior-usa.com/home.html is working, Mozilla is working.
Comment 2•20 years ago
|
||
I tried reproducing the problem with
- Windows 2000
- Windows 2003 Server
But not able too,
I have tried with 1.4.2_05 and there comes a dialog which says general exception
and when you click on more button it says unable to load the class
"com.diginet.groopz.suite.ec.applet.GroopzApplet.class"
I have configured java control panel not to use browser setting and I was using
a proxy so no way control panel knows where to get access from also.
Also tried the same in Tiger-Beta2(1.5 beta 2) but result is same though here it
don't popup any dialog, but a white box instead of applet with red cross on top
left and status displaying "Loading Java Applet Failed..." though i wonder why
they need to append "..." to it.
So can't see any lock here.
Comment 3•20 years ago
|
||
I encounter this problem fairly frequently in Firefox due to a slow
connection... Firefox *eventually* responds once Java has found that it's unable
to load the applet, but while the applet is in the process of trying to load,
Firefox is completely unusable.
Using Firefox 1.0.1 and Java 1.5.0_01 on Windows XP.
Comment 4•20 years ago
|
||
Aha, thanks to bug 142952, I figured out what the problem was in my case:
Adblock. Uninstalling that particular extension made Java work properly again.
Comment 5•20 years ago
|
||
(In reply to comment #4)
> Aha, thanks to bug 142952, I figured out what the problem was in my case:
> Adblock. Uninstalling that particular extension made Java work properly again.
Reporter, does this solve your problem as well? Additionally, could you state
any recent Mozilla Suite / Mozilla Firefox builds (release or trunk) on which
this problem occurs?
Reporter | ||
Comment 6•20 years ago
|
||
I no longer see this problem with Firefox 1.0+, Adblock v0.5 d2 build 39 and Sun
Java 1.5.0_01+ for Windows (possibly 1.5.0 too), however it maybe that the
websites and web proxies work better now.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Comment 7•20 years ago
|
||
I am closing this bug as even reporter is also not able to replicate it anymore.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•