Date: Thu, 10 Jul 2014 15:47:34 +0100 (BST) From: Anton Shterenlikht <mexas@bris.ac.uk> To: corbe@corbe.net, mexas@bris.ac.uk Cc: freebsd-questions@freebsd.org Subject: Re: swamped with >100 npviewer.bin processes Message-ID: <201407101447.s6AElYWa081401@mech-cluster241.men.bris.ac.uk> In-Reply-To: <ygf1tttcnz1.fsf@corbe.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>From corbe@corbe.net Thu Jul 10 15:39:50 2014 > >Anton Shterenlikht <mexas@bris.ac.uk> writes: > >> Not sure which list to address this. >> >> I use nspluginwrapper-1.4.4_3 with firefox, >> as per Handbook. Just noticed that I have 174! >> npviewer.bin processes after firefox is closed. >> Is this expected? >> >> The processes consume a large chunk of memory, >> and refuse to disapper. I can kill them one by >> one, but... >> >What do you mean by they refuse to die? That they keep running, long after their parent process, the firefox, has terminated. >I've had massive issues in the past with npviewer. It's directly >related to the linux flash plugin. > >I keep lots of tabs open so I usually end up with a massive amount of >these things running and consuming a very low amount of CPU usage -- and >as you stated -- quite a big chunk of memory too. > >Doing a 'killall -9 npviewer.bin' every so often solves the problem for >me. ok, so it's not just me. I'll try doing this, but does this not merit a PR? Anton
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201407101447.s6AElYWa081401>