1092623 - Firefox gets stuck when loading a page, device runs hot

Status: RESOLVED DUPLICATE of bug 1085554

(Firefox for Android Graveyard :: General, defect)

Description

[Axel Boldt]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.111 Safari/537.36

Steps to reproduce:

Running Android 4.2.2 (Cyanogenmod 10.1) on Samsung Galaxy S2. After having used Firefox for a while and then putting the phone away, I sometimes find that the phone runs hot. 

In some situations (can't reliably reproduce), Firefox will refuse to load any webpages; it gets stuck at the stage when about one fifth of the orange line underneath the search bar has appeared. I can cancel the page loading and interact with Firefox, but any other page will also get stuck at the same stage. Closing Firefox (with the hardware back button) and opening it again doesn't help. The device runs hot.

In one of these situations, I took a log with aLogcat Root; it can be found at http://pastebin.com/XvWa7PNw

Comment 1

[Aaron Train [:aaronmt]]

Is this with Firefox 33 on Google Play? Can you try out Nightly (http://nightly.mozilla.org) for a while and report back here if that is better? We have a significant number of improvements on Firefox 36 (Nightly) currently.

Comment 2

[Axel Boldt]

This is Firefox 33 on Google Play. Will try nightly now.

Comment 3

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Thanks for the report, Axel. Looking at the log in comment 0, e.g.:

I/IdleService( 5728): DailyCallback running
I/IdleService( 5728): DailyCallback resetting timer to 81908382 msec
I/IdleService( 5728): DailyCallback running
I/IdleService( 5728): DailyCallback resetting timer to 81908374 msec
I/IdleService( 5728): DailyCallback running
I/IdleService( 5728): DailyCallback resetting timer to 81908366 msec
I/IdleService( 5728): DailyCallback running
I/IdleService( 5728): DailyCallback resetting timer to 81908357 msec
I/IdleService( 5728): DailyCallback running
I/IdleService( 5728): DailyCallback resetting timer to 81908349 msec

dupe with bug 1085554?

Comment 5

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

(In reply to Axel Boldt from comment #0)
> Closing Firefox (with the hardware back button) and opening it
> again doesn't help. The device runs hot.

Unlike some other Android applications, when Firefox is closed with the back button, we do not remove it from memory - this is to avoid having to reload the platform, Gecko, on next launch, which can take a while on low-end devices. Swiping Firefox closed in the Recent Applications screen should fully close it.

If this happens again, I recommend using this swipe-to-close technique and relaunching Firefox.

I would like to note that I've seen cases where Firefox stops loading pages (a white content area is shown and the progress bar is stuck) and the only way to fix it is swipe-to-close, but I have not taken a logcat, nor did I wait long enough for the device to get hot (if it was going to). I think there's another bug for that around here somewhere...

Comment 6

[Axel Boldt]

I have since tested the nightly 36.0a1.

I have not yet seen the hanging behavior described in my bug report, but the device still runs hot. Here is a reproducible test case:

Open news.google.com in Firefox Android, then use the device's power button to switch off the screen. Wait an hour. The device will be hot. With the stock Android browser the device remains cool.

Comment 7

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

(In reply to Axel Boldt from comment #6)
> Open news.google.com in Firefox Android, then use the device's power button
> to switch off the screen. Wait an hour. The device will be hot. With the
> stock Android browser the device remains cool.

Axel, is the logcat still filled with messages like:

I/IdleService( 5728): DailyCallback running
I/IdleService( 5728): DailyCallback resetting timer to 81908382 msec

?

Comment 8

[Richard Newman [:rnewman]]

As of yesterday's Nightly (Bug 1085568), these should now be GeckoIdleService, and they'll log at DEBUG.

Comment 9

[Axel Boldt]

Tried with the newest nightly. Phone with Firefox on Google News with switched off screen still runs hot and shows GeckoIdleService messages. Logs are attached.

Comment 10

[Axel Boldt]

Attachment: Logs from 2014-11-04 nightly running hot

Comment 11

[Axel Boldt]

I should add: it appears that the phone runs hot only if it is being charged. So here are the steps:

1. Insert charging cable into device and plug it in.
2. Load news.google.com (other pages seem to do the same) into Android Firefox
3. Use power button to switch off screen
4. Phone gets hot after 30-60 minutes.

Same procedure with a different browser, or without the charging cable, will not run hot.

(Samsung Galaxy S2, Cyanogenmod 10.1, Android 4.2.2, Firefox 36.0a1 nightly 2014-11-05)

Comment 12

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

I think this is still due to the issues in bug 1085554 - we can revisit if fixing that bug does not solve these issues.

Comment 13

[Chris Peterson [:cpeterson]]

Removing steps-wanted keyword because this bug has been resolved.

Comment 14

[Chris Peterson [:cpeterson]]

Removing steps-wanted keyword because this bug has been resolved.