Closed Bug 479254 Opened 16 years ago Closed 14 years ago

Loading java applet hangs

Categories

(Core Graveyard :: Plug-ins, defect)

1.9.0 Branch
x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: nagyt, Unassigned)

References

()

Details

(Whiteboard: [closeme 05-05-2010])

User-Agent: Mozilla/5.0 (X11; U; Linux i686; hu-HU; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; hu-HU; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6 Using the orange button "BELÉPÉS" below the blue bar "CIB INTERNET BANK" on the right side of the website www.cib.hu tries to load a java applet, but it hangs firefox and the popup window also. The java_vm and firefox together use 100% processor resource. The java plugin used is: Java(TM) Plug-in 1.6.0_12-b04 The same operation works on windows without any problem. Reproducible: Always Steps to Reproduce: 1.http://www.cib.hu 2.Click the orange button "BELÉPÉS" below the blue bar "CIB INTERNET BANK"
More informations about the processes: 4485 ntibor 20 0 2336m 103m 26m R 99 5.2 6:41.79 firefox 4022 ntibor 20 0 222m 43m 15m S 12 2.2 0:20.34 java_vm On my AMD Athlon X2 dual core machine with 32 bit OpenSuSe 11.1 firefox uses 100% cpu resources and java_vm only 12%. The killing of java_vm does not help, firefox must be killed also.
The following URL can be used directly to reproduce the problem: https://ibank.cib.hu/Applet2.html
This is wfm with Firefox3.0.6 and JRE1.6 U11 on win32. I think this could be an issue with the linux java plugin and not gecko.
Does this work with another browser on linux ?
I tried it with konqueror (KDE 4.1.3 "release 4.9"), it does not work either, but at least konqueror does not hang. The Applet window does not hang either and I can start a java console. I see the following: ****************** Java VM version: 1.6.0_0 Java VM vendor: Sun Microsystems Inc. Java VM: Sun Microsystems Inc. 1.6.0_0 SecurityManager=org.kde.kjas.server.KJASSecurityManager@1858aa0 ---------------------------------------------------- Konqueror Java Console Help c: clear console g: run garbage collection h: show help m: show memory info s: print system properties t: list threads x: empty classloader cache ---------------------------------------------------- [ APPLET INIT ] [2009.02.20. 13:12:59] DEBUG : Current using version: '5' [2009.02.20. 13:12:59] WARNING : MainApplet.getCodeBase: Codabase setting error. Parameter REMOTE in HTML is invalid. => REMOTE: not exist. Using default codebase. java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:411) at org.kde.kjas.server.KJASProtocolHandler.processCommand(KJASProtocolHandler.java:312) at org.kde.kjas.server.KJASProtocolHandler.commandLoop(KJASProtocolHandler.java:89) at org.kde.kjas.server.Main.main(Main.java:175) ************************************* By the way, does the URL above work at you?
I'm a win32 user with Seamonkey and File name: C:\Program Files\Java\jre6\bin\new_plugin\npjp2.dll / Java Plug-in 1.6.0_11 for Netscape Navigator (DLL Helper) and it works fine, i get 2 security warnings from the plugin itself and after that I'm at a login screen.
Component: General → Plug-ins
Product: Firefox → Core
QA Contact: general → plugins
Version: unspecified → 1.9.0 Branch
OK, but it's about linux.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.4) Gecko/20100413 Firefox/3.6.4 Please update if you are able to still reproduce with the latest nightly build ftp://ftp.mozilla.org/pub/firefox/nightly/latest-trunk/
Whiteboard: [closeme 05-05-2010]
Closing since now after whiteboard closeme date and no reply to last comment. Please reopen/comment with further info, if you still see this issue with Firefox 3.6.13 or later, with a clean profile and the latest version of the plugin. If you wish, you can also try to reproduce in Firefox 4 Beta 8 or later: http://www.mozilla.com/en-US/firefox/all-beta.html
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.