[Opera-Linux] What's with all the "pipe" FDs in Opera?

[Kenneth Crudup]

On Fri, 26 Jun 2009, Eirik Byrkjeflot Anonsen wrote:

> Even with plug-ins active (which your next post may indicate they are
> after all...) it's hard to see any reason to create so many of them.

Well, last night, I could browse. Went to bed, can't go anywhere (stuck
in "Completed request to <site>". Check on the open files, and get:

----
$ sudo lsof -p 25529 | egrep 'pipe$' | wc -l
108
$ sudo lsof -p 25529 | fgrep /home/kenny/.opera/cache | wc -l
773
----

... and I'm up to a bunch of open FDs again:

----
sudo lsof -p 25529 | tail -10
opera   25529 kenny 1109w  FIFO                0,6             6681435 pipe
opera   25529 kenny 1112r  FIFO                0,6             6681440 pipe
opera   25529 kenny 1113w  FIFO                0,6             6681440 pipe
opera   25529 kenny 1114w  FIFO                0,6             6681442 pipe
opera   25529 kenny 1115r  FIFO                0,6             6681445 pipe
opera   25529 kenny 1116w  FIFO                0,6             6681445 pipe
opera   25529 kenny 1119r  FIFO                0,6             6681522 pipe
opera   25529 kenny 1120r  FIFO                0,6             6681450 pipe
opera   25529 kenny 1121w  FIFO                0,6             6681450 pipe
opera   25529 kenny 1122w  FIFO                0,6             6681522 pipe
$
----

> Maybe if we are spawning new pluginwrappers and fail to kill off the old
> pipes.  That would create two new pipes every time, I guess.

What's funny is I see an operapluginwrapper running, which as I'd pointed
out in that other E-mail, shouldn't be happnening if plugins aren't turned
on, right?

> Open files is even harder to understand.  Even if we fail to set
> CLOEXEC, the file descriptor in the origin process should be closed and
> gone when we close the file.  So that sounds like we're not closing the
> files properly.  Which is really strange.

Yabbut the open cache files are in the opera process themselves, not the
plugin wrappers, right? The operapluginwrappers never have many files open
nor misbehave, for that matter (in fact, I haven't seen any runaway
pluginwrappers (spinning in a tight loop with 98% CPU) in a long while).

> I don't suppose you have any way to reliably reproduce?  And even less a
> way to have us reproduce it?

Well, I guess I could send one of you guys privately one of my saved opera
session files and my opera6.ini; that should help with this (even if you
get a look into the way my mind works :)

	-Kenny

-- 
Kenneth R. Crudup  Sr. SW Engineer, Scott County Consulting, Los Angeles
O: 3630 S. Sepulveda Blvd. #138, L.A., CA 90034-6809      (888) 454-8181