Closed Bug 542784 Opened 14 years ago Closed 14 years ago

[OOPP][Linux] Flash, Java, etc. not work with out of process plugins and causes Firefox to become unresponsive

Categories

(Core Graveyard :: Plug-ins, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: erappleman, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.2pre) Gecko/20100128 Ubuntu/10.04 (lucid) Firefox/3.6pre
Build Identifier: Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20100128 Ubuntu/10.04 (lucid) Minefield/3.7a1pre 

Using a trunk build with the Flash plugin installed, visit any website with Flash content.

Firefox will become unresponsive and have to be forcibly closed. 

Some error messages include:

** (firefox-3.7:8607): WARNING **: Serious fd usage error 14
** (firefox-3.7:8607): WARNING **: Serious fd usage error 12

Backtrace:

0x00a99422 in __kernel_vsyscall ()



Reproducible: Always
Version: unspecified → Trunk
Component: Plug-ins → IPC
QA Contact: plugins → ipc
I think I'm experiencing the same problem. I'm using Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.3a1pre) Gecko/20100128 Ubuntu/9.10 (karmic) Minefield/3.7a1pre ID:20100128044501 with 64-bit Shockwave Flash 10.0 r42
Summary: Flash does not work with out of process plugins and causes Firefox to become unresponsive → Flash, Java, etc. not work with out of process plugins and causes Firefox to become unresponsive
Yeah, this bug pretty much applies to practically every plugin out there.
Same bug, please try to fix it asap- it's impossible to use FF with such a big bug=(
What version of Flash?
Blocks: OOPP
Component: IPC → Plug-ins
QA Contact: ipc → plugins
Summary: Flash, Java, etc. not work with out of process plugins and causes Firefox to become unresponsive → [OOPP][Linux] Flash, Java, etc. not work with out of process plugins and causes Firefox to become unresponsive
(In reply to comment #0)
> ** (firefox-3.7:8607): WARNING **: Serious fd usage error 14
> ** (firefox-3.7:8607): WARNING **: Serious fd usage error 12

http://git.gnome.org/browse/ORBit2/tree/linc2/src/linc-connection.c#n929
Same problem here with same configuration than Michael except 32 bits instead of 64 bits. (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20100204 Ubuntu/9.10 (karmic) Minefield/3.7a1pre).

But this problem seems to come from ubuntu packaging (ppa repositories), since if I download nightly build directly from ftp, 
(Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20100204 Minefield/3.7a1pre) it works (i even retrieve the flash working with WindowlessDisable set to false).

Maybe something to check with the way ppa wrapping scripts launch firefox?
If that's the case, has someone filed a bug at https://bugs.launchpad.net/ubuntu/?
The place to report the bug (if this is really packaging related) should be "PPA for Ubuntu Mozilla Daily Build" mailing list (https://launchpad.net/~ubuntu-mozilla-daily/+archive/ppa) since it's not yet officially packaged into Ubuntu trunk.
However, their mailing list seems to be inactive (the daily builds are maybe automatic). So I think that we cannot expect support for these packages.
But if you confirm that using tarball instead of repositories solve the problem, this bug could be closed on the Mozilla bugtracker.
I can confirm that this issue does not apply to Mozilla's builds of 64-bit Firefox. Could the problem be because of optimizations made when it was compiled? For instance, my Firefox was optimized for AMD, but Mozilla's builds I think are optimized for Intel.
This is almost certainly a failure to properly find and execute mozilla-runtime. This may be due to the XULRunner/Firefox split that distros use, failure to ship mozilla-runtime, failure to find it in the expected location, or even something really dumb like it isn't marked executable. An strace would probably tell you where we're looking for it.
Is this fixed with Bug 542053?
Depends on: 542053
I'm sorry if I just sent out an unwanted confirmation mail to you all... didn't use bugzilla before :D

I can confirm this bug, with the package from the ubuntu-mozilla-daily team [1], appeared this morning or so, using the package version 3.6.3+nobinonly-0ubuntu2

As mentioned on [2] a workaround would be to set "dom.ipc.plugins.enabled" to false in about:config


[1] https://launchpad.net/~ubuntu-mozilla-daily/+archive/ppa
[2] https://bugs.launchpad.net/firefox/+bug/513887
It looks as though the problem has been solved as of 3.6.5pre.

firefox-3.5:
  Installed: 3.6.5~hg20100421r34093+nobinonly-0ubuntu1~umd1~karmic
  Candidate: 3.6.5~hg20100421r34093+nobinonly-0ubuntu1~umd1~karmic
  Version table:
 *** 3.6.5~hg20100421r34093+nobinonly-0ubuntu1~umd1~karmic 0
        500 http://ppa.launchpad.net karmic/main Packages
        100 /var/lib/dpkg/status
     3.5.9+nobinonly-0ubuntu0.9.10.1 0
        500 http://gpl.savoirfairelinux.net karmic-updates/main Packages
        500 http://gpl.savoirfairelinux.net karmic-security/main Packages
     3.5.3+build1+nobinonly-0ubuntu6 0
        500 http://gpl.savoirfairelinux.net karmic/main Packages
This was an Ubuntu packaging issue.  We forgot to include the new plugin-container binary.  I'll land the change on our 3.7 packaging branch this weekend.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.