Linked by Thom Holwerda on Thu 10th Jun 2010 22:59 UTC
Multimedia, AV It's been a very long wait, but the release is finally here: Adobe has released Flash Player 10.1. Since Flash has come under increasing scrutiny, there's a lot at stake here for Adobe. This release is supposed to use far less resources while still being faster, more stable, and more secure. Update: No 64bit Flash player for now - on any platform. The Linux beta has been axed.
Thread beginning with comment 429748
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by _xmv
by ggeldenhuys on Fri 11th Jun 2010 22:27 UTC in reply to "Comment by _xmv"
ggeldenhuys
Member since:
2006-11-13

Sooooo many inaccurate comments today!

Yes, including yours. :-)

First of all, when your system runs 64 bit, and flash 32bits.. ONLY FLASH has 2gb limitation. You run it into a wrapper until FF 3.6.4 (which has its own wrapper).

On my Ubuntu 10.04 (64-bit) system, if I copy the 32bit flash plugin (*.so file) into Firefox's plugin folder, it doesn't show up at all in the about:plugins page - flash is completely disabled.

So back to the older v10.0 64-bit flash plugin.

Reply Parent Score: 1

RE[2]: Comment by _xmv
by aliquis on Sun 13th Jun 2010 02:33 in reply to "RE: Comment by _xmv"
aliquis Member since:
2005-07-23

Maybe this are two solutions:

"The reason for this is that NSPluginWrapper 'wraps' 32bit plugins in such a way that other 64bit browsers can use 32bit plugins. It does this by creating a 64bit executable named 'npwrapper.originalpluginname' for each 32bit plugin and this in term runs the real 32bit executable. This works very nicely for Firefox, which cannot handle plugins of a different architecture itself.

Opera however, doesn't need NSPluginWrapper and indeed all it does is serve to cause our own wrapper (which performs the same purpose) to get confused, since we detect the architecture of the NSPluginWrapper (64bit) instead of the actual plugin (32bit). What we need to do is ignore all NSPluginWrapper wrapped plugins by default and indeed there is a bug filed suggesting we do exactly that. In the mean time we do have a system for setting certain plugins to be ignored."

Reply Parent Score: 3