1165345 - Tablet Site does not load

Status: RESOLVED DUPLICATE of bug 1158309

(Firefox for Android Graveyard :: General, defect)

Description

[Davidgleich]

User Agent: Mozilla/5.0 (Android; Tablet; rv:38.0) Gecko/38.0 Firefox/38.0
Build ID: 20150506023541

Steps to reproduce:

1. Go to e.g. www.Augsburger-allgemeine.de
2. open some articles in new tabs but don't switch to all of them directly
3. Go to the next tab and stay a bit
4. Go to another tab


Actual results:

The other tabs just show a white screen and you can't reload any page or follow a link

Comment 1

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

Which device are you using? I wonder if this is a low memory issue.

I can't fully reproduce but I do notice that there is a large delay after pressing a tab (when the page will clear to a white background) and showing the new tab's page content so that the page is all white for an extended period of time. See bug 1116313 on slow tab switching. 

Notably, I'm also having low performance on this page on my N7 (however, that could be from pulling content from distant servers in the background while I try to interact with the page rather than high cpu or memory usage of the page itself).

Sounds like this could be because of bug 1160850.

Comment 2

[Davidgleich]

Using an actually new Samsung Galaxy tab 4 with LTE (SM -T535). today I could reproduce bug 1116313 as well. But after some time it became even worse and I had the same bug as yesterday again.
 Bug 1160850 I could not reproduce because it already happens when I open some tabs they don't need to be used a already. But after closing Firefox and reopening I had them in my history. I even had a look at Samsung's RAM manager and it showed 200mb free left.

Comment 3

[Davidgleich]

I got a similar issue on Facebook probably caused by the same bug: when I scroll down in the timeline sometimes the site doesn't continue to load and links are not clickable anymore. Or the texts and images aren't shown sharp anymore. I will attach a screenshot when I get the issue again.

Comment 4

[Davidgleich]

Attachment: unsharp Facebook timeline

Comment 5

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

Teodora, have you seen anything like this before?

(In reply to Davidgleich from comment #2)
> I even had a look at Samsung's RAM
> manager and it showed 200mb free left.

While we try not to use memory we don't have to, we don't needlessly limit the amount of memory we use - Android will alert us when our memory use negatively affects the other applications on the device so we wait for those notifications before pruning our memory. As such, it's not surprising so little memory is left available.

However, it is interesting that this issue occured around the time I'd expect Android to alert us about low memory, making me think we may not be handling the low memory notifications correctly.

Richard, have we made any recent changes to the Android low memory pruning algorithms that could have affected this?

Comment 6

[Richard Newman [:rnewman]]

The original report sounds like Bug 1151102. IIRC thumbnailing still works, so if you see tab thumbnails but the page stays blank, that sounds like the culprit.

snorp fixed Bug 1106827 in 39, but it sounds like this report is for 38. I don't think there are any memory pressure changes in 38.

Comment 7

[Teodora Vermesan (:TeoVermesan)]

I was able to reproduce bug 1116313 on Nexus 7 (Android 5.1). This is how thumbnails look in tab tray: http://i.imgur.com/ZoBKNdG.png. But I wasn't able to reproduce Bug 1160850.

Regarding this issue:
"The other tabs just show a white screen and you can't reload any page or follow a link"
-> I have only encountered this on my personal phone (Nexus 4 (Android 5.1)) a few time ago, after updating Nightly and open it, pages were blank and refreshing the page, nothing happened.

Comment 8

[Teodora Vermesan (:TeoVermesan)]

Tested with:
Device: Moto X (Android 4.4.4)
Build: Firefox for Android 39 Beta 1 build 2

With no steps to reproduce, after syncing and browsing a few history, I'm getting blank pages. If I load a new tab and navigate to a website or open a page from History, it shows a white screen. Reloading the page or closing it, has no action. 

Please see the following video: https://www.youtube.com/watch?v=z8GnTEnDxcE&feature=youtu.be

Comment 9

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

Do mind testing to see if you can reproduce the issue on the latest Nightly build [1]? It might be related to...

(In reply to Teodora Vermesan (:TeoVermesan) from comment #8)
> With no steps to reproduce, after syncing and browsing a few history, I'm
> getting blank pages. If I load a new tab and navigate to a website or open a
> page from History, it shows a white screen. Reloading the page or closing
> it, has no action. 

bug 1158309?

Which is only fixed as of Firefox 40 (though it is expected to get into 39, which is Beta).

[1]: ftp://ftp.mozilla.org/pub/mobile/nightly/2015-05-21-03-02-04-mozilla-central-android-api-11/

Comment 10

[Davidgleich]

I tested on the official beta(39.0) from google play and was not able to reproduce it so seems to be already fixed in the beta I will go on checking it so seems to be fixed then

Comment 11

[Davidgleich]

(In reply to Davidgleich from comment #10)
> I tested on the official beta(39.0) from google play and was not able to
> reproduce it so seems to be already fixed in the beta I will go on checking
> it so seems to be fixed then

On closing Firefox after typing the comment I could reproduce the error on closing Firefox: on closing Firefox from the menu it did not respond on the first time I needed to do it twice again

Comment 12

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

(In reply to Davidgleich from comment #11)
> On closing Firefox after typing the comment I could reproduce the error on
> closing Firefox: on closing Firefox from the menu it did not respond on the
> first time I needed to do it twice again

I'm sorry but I'm not sure I understood this – is there another issue associated with the bug that the menu becomes unresponsive (along with not being able to load pages) and then you were able to reproduce this other issue on Beta when you tried to quit via the menu?

Comment 13

[Davidgleich]

Yes i mentioned this problem before. It allways appeared after I got the actual issue. But now it seems that the actual issue is fixed in the Beta but the error on closing still appears.

Comment 14

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

Did you mention it in this bug? I can only find references to menu in comment 11 and comment 12.

If it's another bug, do you mind linking me?

I'm going to dupe this to bug 1158309 and we can either use the other bug you link for the menu issue, or we can file a new bug.