Google Chrome won't die

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Google Chrome won't die

Jonathan Ryshpan
Attempting to terminate google chrome by clicking the "X" window decoration closes sometimes leaves some of chrome's back end in existence. When this happens, further attempts to start chrome fail and parts of the system lock up in strange ways. Entering "$ chrome" into a shell locks up the shell; "^C" and "^Z" have no effect; the process(es) can't be killed by using "kill -9 <whatever>"; if the user logs out, no login is possible and the system has to be rebooted.  

Terminating chrome by using the build in exit command: [Customize and control Google Chrome]->Exit work OK.

Has anyone else seen this? What's going on?

Thanks - jon


_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Google Chrome won't die

Tom Horsley-5
On Sat, 12 Aug 2017 15:15:06 -0700
Jonathan Ryshpan wrote:

> Has anyone else seen this?  What's going on?

I haven't seen it that bad, but there is a setting buried
down in the advanced stuff somewhere that says if chrome
should really exit or if it should hang around in the
background to bog down your system.

Found it:

Settings > Advanced > System > Continue running background apps
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Google Chrome won't die

Jonathan Ryshpan
On Sat, 2017-08-12 at 18:29 -0400, Tom Horsley wrote:
On Sat, 12 Aug 2017 15:15:06 -0700
Jonathan Ryshpan wrote:

Has anyone else seen this? What's going on?
I haven't seen it that bad, but there is a setting buried down in the advanced stuff somewhere that says if chrome should really exit or if it should hang around in the background to bog down your system. Found it: Settings > Advanced > System > Continue running background apps

That seems to fix things. But this looks like a pretty serious bug for chrome hanging around to lock up the system.

Thanks - jon



_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]