New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 15 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2015
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

64-bit chromium should be able to support loading 32-bit plugins

Reported by evan.te...@gmail.com, Jun 24 2010

Issue description

Chrome Version       :

Chromium	5.0.375.70 (Developer Build 0)
WebKit	533.4
V8	2.1.10.13
User Agent	Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.70 Safari/533.4
Command Line	 /usr/lib64/chromium-browser/chrome

Sorry if this is a dup.

Because chrome/chromium runs plugins in a separate process and uses IPC to handle communication between the actual browser and the plugin's process, it should be able to support loading both 32-bit and 64-bit plugins in the 64-bit build. Obviously a 64-bit process is capable of launching a 32-bit or a 64-bit process.

This is essentially what things like "nspluginwrapper" do already. But unlike firefox (well until 3.6.4, which now runs things in a separate process), chrome/chromium is already designed to run plugins in a separate process.

Obviously it is a over-simplification, but the way I envision such a feature working (at least in the *nix family) is having a separate 32-bit binary for handling 32-bit plugins. After the usual fork is executed, simply parse the ELF file header and determine if it is 64-bit or 32-bit, then optionally execve the 32-bit plugin handling binary.
 
Labels: -Area-Undefined Area-Internals Internals-Plugins OS-Linux
We're going to be doing this for the Mac; hopefully most of the code will be shareable.

Comment 2 by karen@chromium.org, Jul 2 2010

Labels: Mstone-X
Status: Untriaged
Status: Available
Labels: -Internals-Plugins Feature-Plugins

Comment 6 Deleted

Comment 7 Deleted

Comment 8 Deleted

Comment 9 by staff...@gmail.com, Nov 7 2011

What does Status:Available + Mstone-X mean? 
Is the problem solved but not merged into a release?
See the bug status descriptions at:
http://www.chromium.org/for-testers/bug-reporting-guidelines
Available means it's acknowledged as a bug but not currently assigned to anyone.
Found the answer: http://dev.chromium.org/Home/chromium-security/security-bug-lifecycle/cheat-sheets. 
Would be great if was someone could fix it for Linux. My use case is that I need to run the java plugin in 32 bits because Webex crashes otherwise.

Comment 12 by evan@chromium.org, Jun 11 2012

Cc: -evan@chromium.org
(Un-ccing myself from bugs.)
Project Member

Comment 13 by bugdroid1@chromium.org, Mar 10 2013

Labels: -Area-Internals -Feature-Plugins Cr-Internals Cr-Content-Plugins
Project Member

Comment 14 by bugdroid1@chromium.org, Apr 6 2013

Labels: Cr-Blink
Project Member

Comment 15 by bugdroid1@chromium.org, Apr 6 2013

Labels: -Cr-Content-Plugins Cr-Internals-Plugins
Status: WontFix
Chrome for Linux no longer supports NPAPI plugins.

Sign in to add a comment