Is it just me? After closing Chrome, ps -ef |grep chrome shows a chrome process running for each tab I had open. I have unchecked the option to allow background processes to run after closing chrome.
killall chrome does not kill them.
On Wednesday, August 27, 2014 11:13:54 AM Steven Stern wrote:
Is it just me? After closing Chrome, ps -ef |grep chrome shows a chrome process running for each tab I had open. I have unchecked the option to allow background processes to run after closing chrome.
killall chrome does not kill them.
Not on my system.
Do you quit or close the Chrome window? In any case I would think closing a window when background processess is not enabled be akin to quiting it. You should still try to see how it works when you quit.
On 08/27/2014 11:47 AM, Sudhir Khanger wrote:
On Wednesday, August 27, 2014 11:13:54 AM Steven Stern wrote:
Is it just me? After closing Chrome, ps -ef |grep chrome shows a chrome process running for each tab I had open. I have unchecked the option to allow background processes to run after closing chrome.
killall chrome does not kill them.
Not on my system.
Do you quit or close the Chrome window? In any case I would think closing a window when background processess is not enabled be akin to quiting it. You should still try to see how it works when you quit.
I use the X in the upper right. Using QUIT from it's own menu also leaves processes behind.
I've uninstalled google-chrome-stable, deleted all files left behind, rebooted and reinstalled and still have the problem.
On Wednesday, August 27, 2014 12:22:28 PM Steven Stern wrote:
I use the X in the upper right. Using QUIT from it's own menu also leaves processes behind.
htop will show you the detail of process. I curious what is left behind. Could you please post the chrome line from htop after you QUIT Chrome from menu or Ctrl+Shift+Q.
You should try google-chrome-unstable [ 1] and see if problem is still there. If it then file a bug report and reply with the link here. I would want to follow it.
[1] http://www.chromium.org/getting-involved/dev-channel
On Wed, Aug 27, 2014 at 11:26:15PM +0530, Sudhir Khanger wrote:
On Wednesday, August 27, 2014 12:22:28 PM Steven Stern wrote:
I use the X in the upper right. Using QUIT from it's own menu also leaves processes behind.
htop will show you the detail of process. I curious what is left behind. Could you please post the chrome line from htop after you QUIT Chrome from menu or Ctrl+Shift+Q.
You should try google-chrome-unstable [ 1] and see if problem is still there. If it then file a bug report and reply with the link here. I would want to follow it.
You will also find in GNOME 3 a "phantom" notification in the persistent notification bar at bottom. You can right-click that to deselect the option that allows Chrome to keep running in the background.
On 08/27/2014 04:03 PM, Paul W. Frields wrote:
On Wed, Aug 27, 2014 at 11:26:15PM +0530, Sudhir Khanger wrote:
On Wednesday, August 27, 2014 12:22:28 PM Steven Stern wrote:
I use the X in the upper right. Using QUIT from it's own menu also leaves processes behind.
htop will show you the detail of process. I curious what is left behind. Could you please post the chrome line from htop after you QUIT Chrome from menu or Ctrl+Shift+Q.
You should try google-chrome-unstable [ 1] and see if problem is still there. If it then file a bug report and reply with the link here. I would want to follow it.
You will also find in GNOME 3 a "phantom" notification in the persistent notification bar at bottom. You can right-click that to deselect the option that allows Chrome to keep running in the background.
Since I posted it, of course, has not recurred. But if it does, I'll report back and post a bug on the dev-channel.
On 08/28/14 05:13, Steven Stern wrote:
Since I posted it, of course, has not recurred. But if it does, I'll report back and post a bug on the dev-channel.
It will come back. It does the same thing on my system. Haven't figured out what triggers it. It can be a bit annoying. I use killall /opt/google/chrome/chrome and that does the trick.
On 08/27/2014 03:31 PM, Ed Greshko wrote:
On 08/28/14 05:13, Steven Stern wrote:
Since I posted it, of course, has not recurred. But if it does, I'll report back and post a bug on the dev-channel.
It will come back. It does the same thing on my system. Haven't figured out what triggers it. It can be a bit annoying. I use killall /opt/google/chrome/chrome and that does the trick.
You might consider making that an alias in ~/.bashrc:
alias killchrome='killall /opt/google/chrome/chrome'
will save you lots of typing if it's that much of a problem.
On 08/28/14 06:38, Joe Z eff wrote:
On 08/27/2014 03:31 PM, Ed Greshko wrote:
On 08/28/14 05:13, Steven Stern wrote:
Since I posted it, of course, has not recurred. But if it does, I'll report back and post a bug on the dev-channel.
It will come back. It does the same thing on my system. Haven't figured out what triggers it. It can be a bit annoying. I use killall /opt/google/chrome/chrome and that does the trick.
You might consider making that an alias in ~/.bashrc:
alias killchrome='killall /opt/google/chrome/chrome'
will save you lots of typing if it's that much of a problem.
Don't worry..... I don't type all out. I don't even use that long of an alias. I'm lazy.
On 08/27/2014 05:31 PM, Ed Greshko wrote:
On 08/28/14 05:13, Steven Stern wrote:
Since I posted it, of course, has not recurred. But if it does, I'll report back and post a bug on the dev-channel.
It will come back. It does the same thing on my system. Haven't figured out what triggers it. It can be a bit annoying. I use killall /opt/google/chrome/chrome and that does the trick.
It seems like if I open chrome then quite within a minute or so, it goes wacky. If I leave it open for a long time (hours) it closes OK. I wonder if it has something to do with synchronization.
On 08/27/2014 04:20 PM, Steven Stern issued this missive:
On 08/27/2014 05:31 PM, Ed Greshko wrote:
On 08/28/14 05:13, Steven Stern wrote:
Since I posted it, of course, has not recurred. But if it does, I'll report back and post a bug on the dev-channel.
It will come back. It does the same thing on my system. Haven't figured out what triggers it. It can be a bit annoying. I use killall /opt/google/chrome/chrome and that does the trick.
It seems like if I open chrome then quite within a minute or so, it goes wacky. If I leave it open for a long time (hours) it closes OK. I wonder if it has something to do with synchronization.
Silly thought...are you having it log into Google+ or Google Chrome when it starts up? That might delay a shutdown if you don't log out first.
I never seem to have a problem with Chrome shutting down when I close all the tabs/windows and such, but I also don't let it automatically log into Google's stuff. I never do ANY auto-login stuff. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - "People tell me I look at the dark side. That's not true. I have - - the heart of a small boy......in a jar right here on my desk." - - -- Stephen King - ----------------------------------------------------------------------
On Thursday, August 28, 2014 06:31:23 AM Ed Greshko wrote:
It will come back
Again see the problem exist in unstable version and if it does file a bug. That is the best possible solution.
On Thu, Aug 28, 2014 at 10:02:44AM +0530, Sudhir Khanger wrote:
On Thursday, August 28, 2014 06:31:23 AM Ed Greshko wrote:
It will come back
Again see the problem exist in unstable version and if it does file a bug. That is the best possible solution.
If the GNOME solution I already posted doesn't work, you can also go into Settings in Chrome and turn off the option marked "Continue running background apps when Google Chrome is closed."
On Thursday, August 28, 2014 09:05:08 AM Paul W. Frields wrote:
If the GNOME solution I already posted doesn't work, you can also go into Settings in Chrome and turn off the option marked "Continue running background apps when Google Chrome is closed."
I don't use GNOME and I don't have this problem. I think Background apps are an essential functionality and should not be blocked indefintely if they cause problems.
You should definitely file a bug if you encounter one.
-
Ed Greshko -
Joe Zeff -
Paul W. Frields -
Rick Stevens -
SternData -
Sudhir Khanger