627812 - When lots of tabs are open: tabs all become gray & clicking 'x' has no effect

Status: RESOLVED DUPLICATE of bug 627868

(Firefox for Android Graveyard :: General, defect)

Description

[Daniel Holbert [:dholbert]]

STEPS TO REPRODUCE:
 1. Go to http://m.digg.com and open all/most of the front page stories in new tabs.
 2. Click around between the tabs; if everything's fine, load a few more stories.

ACTUAL RESULTS:
 - After some threshold (around 12 tabs), every tab's content just becomes gray.  The thumbnails are still there, when I switch to the tab, the content area is gray. (with an odd darker-gray stripe going down the screen, too - that's probably just random)
 - I can try to close my now-busted tabs with the red 'x' buttons, they largely are ineffective.  (A few tabs close, but after that point, the remaining tabs refuse to close. The red 'x' changes color when I press & release it, like it normally does to indicate it's being pressed, but the tab remains in my tab strip.)

I think this is fallout from bug 624652.

Comment 1

[Daniel Holbert [:dholbert]]

(In reply to comment #0)
>  - I can try to close my now-busted tabs with the red 'x' buttons, they largely
> are ineffective.

er "When I try"

Comment 2

[Daniel Holbert [:dholbert]]

(I'm running today's nightly using a fresh profile on the Nexus S)

Comment 3

[Daniel Holbert [:dholbert]]

Once you get in this state, the only way to make Fennec usable again is to kill it manually (for users who know how to do that).

Otherwise, you have to wait for the OS to kill it. (however long that takes -- it might actually take a while, because right now I'm not actually in a very low-memory condition -- TasKiller says I have 106 MB of memory free)

Comment 4

[Mark Finkle (:mfinkle) (use needinfo?)]

bug 621779 will handle opening a crazy number of tabs blocking the content area. But I don't think that is what this bug is about.

Gray screens sounds like OOM to me. What device are you using?

Comment 5

[Daniel Holbert [:dholbert]]

(In reply to comment #4)
> bug 621779 will handle opening a crazy number of tabs blocking the content
> area. But I don't think that is what this bug is about.

Yup, this is a different issue. I can still see the content area, and pan up to the URL bar etc. -- it's just that nothing ever loads from this point on, and the content areas are all gray.  (And the 'x' buttons don't work)

> Gray screens sounds like OOM to me. What device are you using?

Nexus S.

(Note that the device remains pretty responsive throughout this whole time, though, and after I've gotten into this state, TasKiller says I have 106 MB of memory free.)

Comment 6

[Doug Turner (:dougt)]

mark, i think maybe this is the resurrect code doing bad things.  OOM, yes.  The browsers are gone; tabs are still up.  However clicking on the tabs do not do anything.  clicking on the X on the tab doesn't close the tab.

Comment 7

[Mark Finkle (:mfinkle) (use needinfo?)]

(In reply to comment #6)
> mark, i think maybe this is the resurrect code doing bad things.  OOM, yes. 
> The browsers are gone; tabs are still up.  However clicking on the tabs do not
> do anything.  clicking on the X on the tab doesn't close the tab.

Sounds like the display viewport is not being setup. This normally happens when a tab is selected. Looping in Wes since he is familiar with display viewports and is local to dholbert.

Any errors in the JS console?