On Sun, 2015-01-11 at 17:42 -0500, Fred Smith wrote:
On Sun, Jan 11, 2015 at 05:12:48PM -0500, Bill Maltby (C4B) wrote:
On Fri, 2015-01-09 at 19:42 -0500, Fred Smith wrote:
<snip>
In a nutshell, after I would terminate Firefox as part of my normal log off process, there would be another instance of Firefox left hanging around with a ppid of 1 (so it's daemonized", or as I prefer "demonized" ;-)) and using all the CPU it could get (97%-99% of a 6 core AMD in my desktop) while no Firefox windows were open. Figuring it might be saving stuff I checked back many minutes later on many days and cycles and it was always there. Moreover, when normally using Firefox I'd seen 103%, 104% CPU usage etc.
I commonly also find a "stray" firefox running after stopping firefox, and it isn't using a window either. it's a nuisance because, when there's a firefox update and it wants to restart the browser, it can't because there's that darn "stray" one hanging around.
like you, I have no idea where it comes from or why it's there, nor what it's doing, either.
I commented out the entries that start it in Xclients and made a patch. If I see no ill effects I'll leave it in place, otherwise back to digging as to why it's there.
please let me know how it goes, I may want to investigate doing the same.
After my first restart of X, things are working well but I did see an abrt of a gnome pkg-something manager. No other ill results thus far. I ignored the abort because, based on the results of my bug filing on the X window crash (when moving between run levels 3 and 5) so far, there's no benefit to investigating and reporting it.
The patch is small so I'll attach it in case anyone else wants to give it a go right now.
<snip>
Bill