My Google Chrome frequently hangs for no apparent reason. Application is active (responding), but tabs are blank and nothing loads... The only solution that I found is to go into Settings -> Apps -> Google Chrome and "force close" it. Then I re-open it, and it works OK again, for some time.

I'd like to automate this manual "force close" process, e.g. I'd like to have a shortcut on my screen that terminates Chrome for me. Any other easy way to close Chrome is acceptable too.

My device is Asus Transformer, rooted.

  • You can get halfway there by adding a shortcut to apps settings. – ale Jun 26 '12 at 19:23
  • Maybe try Dolphin Browser, it might fare better than Chrome (bear in mind Chrome is still early stages...) – t0mm13b Jun 26 '12 at 19:36

I've ended up using Tasker, it is trivial to create a task to kill a specific application (Google Chrome), than add a shortcut (widget) to that task on the screen.

Edit: I've actually created a task that not only kills Chrome, but restarts it afterwards as well, all in one click:

enter image description here

| improve this answer | |
  • Very neat and handy app, powerful as well :) Good for you, I saw that on twitter, that there's going to be a new Tasker that will enable you to save them as "mini independant programs" outside of Tasker.. – t0mm13b Jun 26 '12 at 22:29
  • Should share what way you've set it up for others benefit :) – t0mm13b Jun 26 '12 at 22:29
  • @t0mm13b: I've added a screenshot of my task, it's pretty self-explanatory. – haimg Jun 28 '12 at 16:31
  • neat... :) I have one here that switches off audio after 19:00, the incessant whine of emails/twitter etc... :D – t0mm13b Jun 28 '12 at 16:36
  • Another option that works well is Automate, although this requires root. – Sparhawk Nov 10 '16 at 5:30

Get a process killing app from the market like 'Advanced Task Killer', it will allow you select which processes you would like to kill and then do so by clicking a single "kill" button.

Warning!! Of course forcibly "killing" a process is not recommended as it can break your application (think of what would happen if a process is writing to file and then is suddenly terminated, you could end up with a corrupt asset!!!) or even, in worse conditions, harm your system.

you will either have to wait for it to close by itself or just use a different browser. so the answer is yes, but don't do this.

| improve this answer | |
  • 1
    Using task Killer is frowned upon, Android != Windows, where you can zap at a process to kill it a lá Windows Task Manager. You could actually end up de-stabilizing Android and... also, drain the battery, in the context of services, kill 'em, they'll end up restarting - juice sucked! which is the very nature of services. Let Android do its job – t0mm13b Jun 26 '12 at 19:27
  • Hence -1 from me for recommending it. The answer is don't...use...any...task...killers...what...so...ever! – t0mm13b Jun 26 '12 at 19:28
  • 1
    actually killing a process (pid) is a linux native method of forcibly closing a process, of course you would use it only in extreme conditions. I guess an edit is in place! – svarog Jun 26 '12 at 19:31
  • Android is not Linux! :) Don't even think it is, just because it has a limited busybox userland tools to mimick a full blown Linux desktop/server.... – t0mm13b Jun 26 '12 at 19:34
  • 4
    @t0mm13b: Although this is not something that I would like to do (still a multi-step process), this one specific case is probably ok task for a task killer. After all, all I want to do is kill a misbehaving task quickly and effortlessly (on demand - not automatically). – haimg Jun 26 '12 at 19:57

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.