6 Mar
2015
6 Mar
'15
11:26 a.m.
Hi Guys,
On Friday 06 March 2015 01:48:16 Steven D'Aprano wrote:
On Thu, Mar 05, 2015 at 10:01:57AM -0700, Jonesy
wrote:
It did the 98% cpu thing again last night. As it happened I had
KsysGuard running, and it showed "nsplugin-container" at 98% cpu.
Using the kill in KsysGuard stopped the process. Iceweasel showed
35% cpu at that point. I assume that the total, 133% cpu, is because
I have a dual core processor.
Thanks all, for the useful information.
--
Best Regards:
Baron
On Thu, 5 Mar 2015, Dan Youngquist wrote:
You shouldn't need to run as root at all. You just need to run as
the same user who ran Iceweasel in the first place. That's likely
to be you.
Oh, and killing Iceweasel/Firefox is probably overkill. If it
actually is Flash causing the problem, you can just kill the Flash
plugin.
ps aux | grep nspluginviewer
if you are using Adobe's Flash plugin. If you are using the
third-part FOSS "gnash" plugin, I think this will work:
ps aux | grep gnash
Once you have the process ID, just kill it as normal:
kill <id>
(Use kill -HUP and kill -9 if necessary). On 03/05/2015 07:27 AM, Lisi Reisz wrote:
And, you should not need to run as root. On Thursday 05 March 2015 10:04:28 Baron wrote:
> Having closed Iceweasel, it still seems to be running
I have had this problem on and off in various versions over
the years. I do:
# ps ax | grep iceweasel
# <response>
# kill xxxx
Faster/easier:
killall -9 iceweasel