Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Whenever it is not active, Firefox Mobile 10 constantly uses 10-40% CPU

  • 3 replies
  • 10 have this problem
  • 9 views
  • Last reply by fuzi0719

more options

Samsung Galaxy S Infuse 4g (aka "Galaxy S 1.5") with Gingerbread.

While it is the active application, Firefox seems to be using reasonable amounts of CPU. If it is not active, though, it constantly uses 10-40%, until it gets background killed, which obviously eats through the battery.

This happens with Sync disabled.

Is there anything I can do about this, aside from file a bug and wait for v11?

Samsung Galaxy S Infuse 4g (aka "Galaxy S 1.5") with Gingerbread. While it is the active application, Firefox seems to be using reasonable amounts of CPU. If it is not active, though, it constantly uses 10-40%, until it gets background killed, which obviously eats through the battery. This happens with Sync disabled. Is there anything I can do about this, aside from file a bug and wait for v11?

All Replies (3)

more options

Hi,

I'm sorry you are having this problem. You can Quit the browser when you aren't using it.

-Michelle

more options

Same problem on Firefox 10.0.4, using Samsung Galaxy S2 on 4.04.

By pressing the Home button, Firefox is put into the background and then starts consuming unacceptable CPU until it's killed.

Manually closing from the menu solves the immediate problem, but makes me want to switch to another browser.

more options

Letting Firefox run like this in the background and eating through a fully-charged battery in less than 3 hours is simply ludicrous. No other Android app I've ever encountered works this way. I use Firefox exclusively on my desktop and laptop and was looking forward to using it on my mobile so I could take advantage of sync. But, after finding my phone completely discharged, as soon as I had enough power to restart, I yanked Firefox off as quick as possible. Not funny. Not acceptable, especially since there is NO WARNING of this behavior. WTH are you thinking??????