quasi-[OT] Adobe Flash

Patrick O'Callaghan pocallaghan at gmail.com
Sun Oct 24 04:58:05 UTC 2010


On Sat, 2010-10-23 at 19:41 -0700, Suvayu Ali wrote:
> Hi Patrick and Marko,
> 
> On Saturday 23 October 2010 03:51 PM, Patrick O'Callaghan wrote:
> > I tried it using inotifywait(1), but it never terminates, i.e. the flash
> > file persists even after the video has finished. I suspect it will stay
> > there till a new video starts or the flash plugin (i.e. the browser
> > process) dies.
> >
> 
> I think I know what is going on. See my explanation below and please
> comment. :)
> 
> > tail -f -q --bytes=1G --pid=${pid} $in_file>  $out_file&
> 
> Firstly that `--pid=${pid}' needs to be removed otherwise it waits for
> the browser to exit.

That wasn't clear originally, but I think you're right.

> But even that won't help.
> 
> When the script executes the above command, another file descriptor is
> opened under the pid for tail. This stays linked to the (deleted)
> /tmp/FlashXXXX file even after the link under the browser's pid has
> been deleted and inotify keeps waiting for the original file to be
> deleted!

Perhaps, but even after killing the grab-flash process the /tmp/Flash*
file still hangs around for a while, so something else is going on. Some
more experimentation is needed.

[... time passes ...]

OK, I took another look and it seems we are talking at cross purposes
here. On my system, using both Firefox and Chromium, the Flash plugin
does *not* delete the buffer file when it has finished playing. The file
only disappears when another file is opened or the browser terminates.

This is on F13 using the 64-bit flash plugin in
libflashplayer-10.0.d20.7.linux-x86_64.so.tar.gz (from Adobe).

If this is a different setup from what you have, I apologize for wasting
everyone's time.

poc



More information about the users mailing list