I started an online transaction on Chrome (under Jelly Bean). In between, I had a phone call and the browser closed automatically. It disconnected from the web sites, and I had to start the transaction again.

Is there any way to keep Chrome running in background and keep all the connections open?

This is really a big problem for now. I fear starting any online transactions on my Jelly Bean device.

Is there any other browser which will keep the connections open?

Google must have come across this issue.

2 Answers 2


This is probably because of the amount of RAM on the device you are using. It sounds like the system gave the RAM that was being used by Chrome to the phone app. It saw that Chrome was no longer the active app and the phone app was requesting more RAM so in order to free up the RAM it had to close Chrome.

If Chrome was using a majority of the system RAM, and a new app requested access to the RAM, the system needed to free some up.

Since you did not specify what device you have though, this is really only a guess.

  • It could be a cause, but IMO his device will not have less than 512MB RAM. I had Sony Xperia Mini with same RAM and had ICS and I used Chrome for long time on it and never get this kind if issue due to RAM on my device.
    – avirk
    Jan 7, 2013 at 13:42
  • @avirk, My Galaxy S Vibrant would do this all the time which has 512MB. Jan 7, 2013 at 15:25

Android has two mechanisms that claim memory back from the applications that you run.

One mechanism is called OOM and is an integral part of linux. It activates only when the memory is really needed for something else. A phone call would normally NOT trigger this mechanism. Playing a game would, or copying large amounts of files from internal storage to SDCARD.

The other mechanism is native to android, and closes applications that have not recently been used. The exact defintion of "recently" is a moving target. It changes with every release of android, and also with the specific modifications that the manufacturer has made to it. Only the application that is currently visible is always recent enough to not be killed under this mechanism, on every version of android.

Apparently on your system and phonecall is enough to trigger that.

You can try two things to avoid this to happen. One is to switch back to Chrome while you talk on the phone. Use the multitasking functionality of your phone to do that. Chrome will then be the most recent app and android should respect that even during long calls. Note that your call wont be killed either under the same mechanism, because it handles audible interaction, which also makes it a currently used app even when not visible.

The other thing to try is an app that I made. Its originally designed to solve this very same problem for the Opera Mobile browser (now called Opera Classic). Its flexible enough to let you use it with Chrome. However I dont know if it really helps, your mileage may vary. You can download it for free here: http://forum.xda-developers.com/showthread.php?t=2269810

There is also another aspect to your problem, namely memory management inside Chrome (not android). I vaguely recall that Chrome can evict tabs from memory when you look at other tabs. If that is true, the above tricks might only help you to keep Chrome itself alive but the previously loaded content may still be gone. In this case, only a new improved version of Chrome can solve your problem, or switching to other browsers.

I know that Opera Classic does not evict single tabs from memory, neither does Opera Mini. They either stay 100% in memory, or they are killed 100% at once. If you dont like those two, you may want to test other browsers specifically for this property and then apply one of the mentioned tricks to keep them always in memory.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .