Red Hat Bugzilla – Bug 976833
Update 18.104.22.168.-22.214.171.124 makes Seamonkey and Firefox to lock up
Last modified: 2013-10-17 13:16:47 EDT
Description of problem:
After update applied on 20/6-2013 Accessing WEB sites with java content browser sleeps forever, can maybe extreem slowly
Version-Release number of selected component (if applicable):
Previous java version
Access this URL fx.http://browserspy.dk/java.php
Steps to Reproduce:
1.install update 126.96.36.199-188.8.131.52.fc17.i686
2.Check above link
Browser locks up.
Showing Java information
Checked out on several other sites..same result, locks up, killed with System monitor
tried undo update and redo update...same result
As interim solution backdated to 184.108.40.206-2.1.fc17
No error after that
Browser plugin is Icedtea 1.7.0_b147-icedtea (22.0-b10)
Are you getting SELinux denials by any chance?
No SElinux is disabled
Anything in ~/.xsession-errors? Can you get the icedtea logs as described on  and attach them to this bug?
Error happend also in Seamonkey 2.17.1 in a virtual vbox FC18 with
With or without the latest java update from 220.127.116.11-18.104.22.168.fc17.i686
I got Icedtea to generate the log in virtual machine
Seems to be Icedtea related as Openjdk 22.214.171.124-126.96.36.199.fc17 contains a Icedtea update
Actually it seems that Seamonkey is not locked up
After 5-6 min the Icedtea debug window pops up with a "serious exception has occurred..."
Applet not initialized.....
After updated Icedtea-web.i686 to 1.3.2-1.fc17 the Openjdk 188.8.131.52-184.108.40.206.fc17.i686 can be applied without problem
Secondary info: Problem still persist in FC18 with Icedtea 1.4.1 and latest Openjdk
As you probably noted, the IcedTea-Web had to be also updated after OpenJDK 220.127.116.11 update.
But seeing this: https://admin.fedoraproject.org/updates/FEDORA-2013-11291/icedtea-web-1.4-1.fc18 It should work.
You may try: reinstall icedtea-web, disable selinux, try other browser.
If other browser will work, then it will be different issue then update to OpebJDK 25.
And will be arch specific - on x86_64 I'm pretty sure it is working.
Just for info:
You suggestion about reinstall ICEDTEA, disab SELinux, Other browser
None of these gives positive result
All tested under fc18 in a virtualbox FC18_i686, very clean system as just installed for test.
But this should be discussed under that Fedora version and not in this bugreport
I am using FC17 for daily work
This is deadlock caused by multiple applets with shared classloader. Assign to adam who rewrote this part of netx.
Strange is that it is reproducibel only on 32 arch.
Can 64b one start up so much more slowly?
I'm having similar problem under Fedora 19. I don't know if it stopped working under F18 already (I've upgraded around week ago) as I'm not using icedtea-web daily.
Behaviour is similar as described earlier, however, I don't get any debug window in about 5 min.
Firefox output from terminal:
/builddir/build/BUILD/icedtea-web-1.4/plugin/icedteanp/IcedTeaNPPlugin.cc:483: thread 0x7f5eaf418b90: Error: Failed to create input pipe: Permission denied
java version "1.7.0_25"
OpenJDK Runtime Environment (fedora-18.104.22.168.fc19-x86_64)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
Error: Unable to fetch applet instance id from Java side.
Error: Unable to fetch applet instance id from Java side.
If I create new profile, Firefox stays responsible, but the result is the same (except the "Error: Unable to fetch applet instance id from Java side." is not printed).
The javatester.org works for me pretty well on f19, 64b
for f19 there was an update of openjdk in meantime, but it should not matter.
Error: Failed to create input pipe: Permission denied
Is very suspicious.
So you have read write permissions on your temp directory? Are other applets working? Cant be anything else blocking the pipe file?
I had wrong permissions on "/var/tmp/icedteaplugin-*". I deleted all the files and it works... Sorry for the intrusion in this bug.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Adam is on vacation for the next few weeks. Re-assigning to Andrew.
Should this bug not be closed ?
Problem does not exist under F17 any more (see my previous post) after update of ICEDtea.
However it persist in F18 in very similiar form, but that should be reported as a bug in F18
I have moved it under f18 - however I'm confused it started to work :)
Just to be clear:
Try this link in f18 (or F19)
(tested in vbox f18)
Either firefox or seamonkey
According to Ksysguard systemmonitor java process hook the CPU.
and browser went unresponsive
closing browser does'nt really kills the browser only possibel with Ksysguard (kill java and browser)
works perfect in f17 (real machine) with
Before latest update to Icedtea-web the java 22.214.171.124 update gave the same problem
Created attachment 771228 [details]
Plugin Debug log for browserspy.dk/java.php
$ rpm -qa | grep -e "icedtea\|openjdk"
Can confirm behaviour on browserspy.dk/java.php with these package versions installed in an FC18 VM. Will investigate.
I think it is fixed in head of ITW (with latest Openjdk)
Still seems to be locking for me (ITW head, F19 x86_64, latest OpenJDK).
This issue has been resolved in IcedTea-Web upstream.