[VDPAU] [PATCH] Detect libflashplayer through /proc/self/maps

[Jeroen Roovers]

On Wed, 20 Nov 2013 09:58:56 -0800
Aaron Plattner <aplattner at nvidia.com> wrote:

> The one I was worried about was Chrome with the PPAPI Flash player,
> but it looks like that's called libpepflashplayer.so and it doesn't
> load libflashplayer.so if the former exists.

Google Chrome dropped the NS plugin interface and went with something
called "pepper". Accordingly the library that Adobe ships specially for
Chrome is called "libpepflashplayer.so". Additionally, it's run OOP so
it's pretty safe to check for.

> The potential for some browser to use VDPAU directly for HTML5
> rendering while libflashplayer is also loaded does make me nervous,
> but given that it fixes Opera and doesn't break Firefox/Seamonkey,
> I'll merge this, assuming your WebKit browser tests don't turn up any
> issues.

jeroen   24065 18.4  2.6 1061708 108416 pts/2  Sl+  17:01
0:15 /opt/google/chrome/chrome --type=ppapi
--channel=23970.4.1372145876 --ppapi-flash-args --lang=en-GB
--user-data-dir=/home/jeroen/.config/google-chrome-beta

Chrome doesn't mention anything of the sort except vaguely through
"ppapi" and "-flash-", so I guess my patch fixes the issue if it's
present at all _or_ Adobe might have "fixed" it some other way.


Regards,
     jer