Hi All,
Debian Jessie, R14. I've noticed an odd thing. Having closed Iceweasel, it still seems to be running and taking 98% cpu according to KSysguard. I had noticed a slowdown in browsing for a few days now, but didn't realise why until last night.
On Thursday 05 March 2015, Baron wrote:
Hi All,
Debian Jessie, R14. I've noticed an odd thing. Having closed Iceweasel, it still seems to be running and taking 98% cpu according to KSysguard. I had noticed a slowdown in browsing for a few days now, but didn't realise why until last night.
Same here with Firefox. Depends on the special page you are looking at (Flash?). Closing some tabs sometimes helps.
Gerhard
Hi Gerhard,
On Thursday 05 March 2015 10:26:21 Gerhard Zintel wrote:
On Thursday 05 March 2015, Baron wrote:
Hi All,
Debian Jessie, R14. I've noticed an odd thing. Having closed Iceweasel, it still seems to be running and taking 98% cpu according to KSysguard. I had noticed a slowdown in browsing for a few days now, but didn't realise why until last night.
Same here with Firefox. Depends on the special page you are looking at (Flash?). Closing some tabs sometimes helps.
Gerhard
Ah, I had noticed that I've had messages that "Flash" has crashed ! I've simply dismissed the message and carried on. I rarely open more than two tabs, though I normally open a "Private Window" when I'm browsing.
I'll take more notice when that happens. Thank you for your reply.
On Thursday 05 March 2015, Gerhard Zintel wrote:
On Thursday 05 March 2015, Baron wrote:
Hi All,
Debian Jessie, R14. I've noticed an odd thing. Having closed Iceweasel, it still seems to be running and taking 98% cpu according to KSysguard. I had noticed a slowdown in browsing for a few days now, but didn't realise why until last night.
Same here with Firefox. Depends on the special page you are looking at (Flash?). Closing some tabs sometimes helps.
should have been expressed: Finding the culprit and closing that page normally helps.
forgotten to mention: No problem of TDE in my opinion. Same problem on Mint with Mate desktop.
Gerhard
On 03/05/2015 07:27 AM, Lisi Reisz wrote:
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
On Thursday 05 March 2015 15:59:19 Dan Youngquist wrote:
On 03/05/2015 07:27 AM, Lisi Reisz wrote:
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
Thanks, Dan!
Lisi
Hi Guys,
On Thursday 05 March 2015 16:49:58 Lisi Reisz wrote:
On Thursday 05 March 2015 15:59:19 Dan Youngquist wrote:
On 03/05/2015 07:27 AM, Lisi Reisz wrote:
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
Thanks, Dan!
Lisi
Thanks ! Both methods noted.
On Thu, 5 Mar 2015, Dan Youngquist wrote:
On 03/05/2015 07:27 AM, Lisi Reisz wrote:
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
And, you should not need to run as root.
Jonesy
On Thu, Mar 05, 2015 at 10:01:57AM -0700, Jonesy wrote:
On Thu, 5 Mar 2015, Dan Youngquist wrote:
On 03/05/2015 07:27 AM, Lisi Reisz wrote:
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
And, you should not need to run as root.
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 Thursday 05 March 2015 04:48:16 pm Steven D'Aprano wrote:
On Thu, Mar 05, 2015 at 10:01:57AM -0700, Jonesy wrote:
On Thu, 5 Mar 2015, Dan Youngquist wrote:
On 03/05/2015 07:27 AM, Lisi Reisz wrote:
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
And, you should not need to run as root.
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).
Re a couple of posts.
If you use the cli to halt a process, use top. top accepts the 'k' or kill command..it uses kill -15....not -9, works here.
I use Iceweasel & Firefox, it hardly ever has any issues. I do not use 'gnash' to problematic, I use flash from Adobe, Debian's package..'flashplugin-nonfree'. The most recent versions of Firefox sandbox Flash well, this has reduced issues with flash , ymmv.
I run Iceweasel, Firefox at the same time..different users, a couple of vbox instances..one of which runs Firefox & flash.. trouble free.
Gnash is useless it has never worked for me and I am surprised it is available in the repositories at all. For Linux Flash is stuck at version 11.2 and will never get any higher but it is version 15.x or 16.x in other systems. In Linux Iceweasel/Firefox now complains about Flash in various sites and even gives a warning in some instances that it may cause degraded browsing performance. Web devs should just move to HTML5 anyway anddump a feature that should have died with the dinosaurs. If you must use Flash you are much better off using Chromium and adding the pepperflash-nonfree plugin or you could just use straight Chrome if you are OK with Google watching your every move (says Michael while he is posting this from his gmail address :) )
On 6 March 2015 at 14:12, Greg Madden gomadtroll@gci.net wrote:
On Thursday 05 March 2015 04:48:16 pm Steven D'Aprano wrote:
On Thu, Mar 05, 2015 at 10:01:57AM -0700, Jonesy wrote:
On Thu, 5 Mar 2015, Dan Youngquist wrote:
On 03/05/2015 07:27 AM, Lisi Reisz wrote:
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
And, you should not need to run as root.
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).
Re a couple of posts.
If you use the cli to halt a process, use top. top accepts the 'k' or kill command..it uses kill -15....not -9, works here.
I use Iceweasel & Firefox, it hardly ever has any issues. I do not use 'gnash' to problematic, I use flash from Adobe, Debian's package..'flashplugin-nonfree'. The most recent versions of Firefox sandbox Flash well, this has reduced issues with flash , ymmv.
I run Iceweasel, Firefox at the same time..different users, a couple of vbox instances..one of which runs Firefox & flash.. trouble free. -- Peace,
Greg
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
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:
On Thu, 5 Mar 2015, Dan Youngquist wrote:
On 03/05/2015 07:27 AM, Lisi Reisz wrote:
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
And, you should not need to run as root.
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).
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.
On Friday 06 March 2015 02:26:52 am Baron wrote:
Hi Guys,
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.
I do not nave 'nsplugin-container', mine says 'plugin-container'....this difference, whatever it is, might explain your issue.
Hi Greg
On Friday 06 March 2015 16:59:15 Greg Madden wrote:
On Friday 06 March 2015 02:26:52 am Baron wrote:
Hi Guys,
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.
I do not nave 'nsplugin-container', mine says 'plugin-container'....this difference, whatever it is, might explain your issue.
I've just checked. Doh ! Yes your right. My mistake. Sorry :-(
On Friday 06 March 2015 01:48:16 Steven D'Aprano wrote:
And, you should not need to run as root.
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.
Something else I've learnt. I thought that ps had to be run as root. I could have sworn that it used to be. I know that until now I hadn't checked recently.
Thanks, Steven.
Lisi
On Thu, Mar 05, 2015 at 07:59:19AM -0800, Dan Youngquist wrote:
On 03/05/2015 07:27 AM, Lisi Reisz wrote:
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
Too fast, too easy. Have you actually tried it?
My prediction is that if you do, you will leave Iceweasel or Firefox stuck in an unrunnable state. By using kill -9 you tell the operating system to just yank the rug out from under Iceweasel, without giving it a chance to clean up after itself. That means:
- anything that needs to be saved to disk won't be;
- the database may be left open, or worse, in an inconsistent state;
- lock files will be left in place.
I'm not willing to try it, but I'm pretty sure that if you do, when you go to run Iceweasel/Firefox again, it will tell you that it is still running. You need to find the two lock files, and delete them both. Worse, you may have screwed up the database, which could leave Iceweasel unable to track history, or destroy your bookmarks.
kill -9 is the equivalent of pulling the power cord. Use it only when everything else fails. Everything else in this case should be:
- try kill <processid> first;
- give it 30 seconds or so, and if it still hasn't closed, try kill -HUP <processid>
- if and only if that too fails, then and only then consider kill -9.
Oh, and I dislike killall, since that risks killing too many processes. If you have something else running with iceweasel in the name, you'll accidently kill that as well. That's just my personal preference though.
On 03/05/2015 05:40 PM, Steven D'Aprano wrote:
On Thu, Mar 05, 2015 at 07:59:19AM -0800, Dan Youngquist wrote:
Faster/easier: killall -9 iceweasel
Too fast, too easy. Have you actually tried it?
um... yes. Many times, with about every task I've ever wanted to kill. Never had any sort of problem.
Faster/easier:
killall -9 iceweasel
How brutal. My advice: 1. Kill only the plugin-container process - that should suffice. 2. Use htop as a replacement for top
Janek
--- Politechnika Łódzka Lodz University of Technology
Treść tej wiadomości zawiera informacje przeznaczone tylko dla adresata. Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją przez pomyłkę prosimy o powiadomienie o tym nadawcy oraz trwałe jej usunięcie.
This email contains information intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient or if you have received this message in error, please notify the sender and delete it from your system.
-
Baron -
Dan Youngquist -
Gerhard Zintel -
Greg Madden -
Jan Stolarek -
Jonesy -
Lisi Reisz -
Michael . -
Steven D'Aprano