Date: Mon, 04 Dec 2006 15:44:18 +0000 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: Pietro Cerutti <pietro.cerutti@gmail.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Acroread never dies Message-ID: <45744252.5070601@dial.pipex.com> In-Reply-To: <e572718c0612040642m4aad42d5idc1b14cb311fe88a@mail.gmail.com> References: <e572718c0612040642m4aad42d5idc1b14cb311fe88a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Pietro Cerutti wrote: > acroread7-7.0.8,1 > acroreadwrapper-0.0.20060221 > firefox-2.0_2,1 > > the Acrobat Reader 7 plugin works just fine, but the acroread process > doesn't die even after the Firefox window containing the object > visualized by the plugin (a PDF document) has been closed. > > The process is displayed in top(1), sometimes in status "select", > sometimes even in status "RUN". > 17468 piter 1 97 0 107M 79776K select 0:06 0.20% > acroread > > I just don't understand why the process stays alive, and what it's > does, when RUNning. It's stays in memory so that th next document that you load, will not require it to start up again. Typical Windows behaviour transmitted to FreeBSD and presumably other OSen as well. Personally I hate that behaviour, since when running in a browser window you have nothing obvious to kill if you know you don't want to read anything else. That's just how it is. Nothing is wrong with your installation. The process as you list it is in select, so it's not actually slowing your machine down, just chewing memory. --Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45744252.5070601>