Firefox hangs when using hava applet JSObject.getWindow()

[Kees]

Binary package hint: firefox-3.0

Firefox hangs (and uses 100% cpu) when java applets use JSObject.getWindow() in combination with XMLlHttpRequests().

If I leave out the new XMLHttpRequest(), it does not happen.

Attached are: HelloWorld.java (13 lines) with the applet code and HelloWorld.class.
Also attached are index.html (38 lines), and gdb.txt with the stack trace of gdb of the running firefox process.

To reproduce: put HelloWorld.class and index.html in a subdirectory of the webserver root directory, e.g. http://localhost/ffbug/.

I've experienced this first in Jaunty. Have tried an Intrepid fresh install, but it didn't happen there, but after updating Intrepid with the update-manager, the problem also appears.

This code is part of a larger application that ran fine under Ubuntu Hardy. I switched to Jaunty mid May this year.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: firefox-3.0 3.0.10+nobinonly-0ubuntu0.9.04.1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.28-11-generic i686

[willsteel (michael-willigens)]

my post on this migth help you:

https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/331962

regards,
michael

[Kees (kees-vanveen)]

Thanks Michael,

Your fix works great!

I've put the new Thread around the JSObject.getWindow() in the init() of
the applet, and my problem is gone. Also tested it on Windows IE, FF and
Chrome, and there it works as well.

Cheers,
Kees

[willsteel (michael-willigens)]

always glad to help someone out.

[Monkey (monkey-libre)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #331962, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.