998152 - [Tarako] going to browser settings and then going back can show a "This is embarassing" page

Status: RESOLVED DUPLICATE of bug 991547

(Firefox OS Graveyard :: Gaia::Browser, defect)

Description

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

1. reboot device
2. launch browser
3. open tab
4. go to settings
5. hit done
6. hit back

Expected: top 4 web pages. (all 4 are text only web pages)
Actual: "This is embarassing"; reload and close tab buttons do not do anything

Gaia      a8d2d399f2939f4845abaa0df57abab241a2c782
Gecko     https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t/rev/d97dad54cb61
BuildID   20140417004002
Version   28.1
ro.build.version.incremental=eng.cltbld.20140417.115200
ro.build.date=Thu Apr 17 11:52:06 EDT 2014
Tarako

Comment 1

[Joe Cheng [:jcheng] (please needinfo)]

ni? Naoki, can the user recover this easily by refreshing the page?
it seems like this will happen on any device if the page itself is high-memory-consuming 
Thanks

Comment 2

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Hi Joe, this doesn't happen on buri.  It's just a simple going to the settings and then coming back.  I can't recall how the images of the webpages are displayed.  We may need some input from either Dale Harvey or Ben Francis.  Having said that I don't think we should be showing this page when the user hasn't even invoked a web page directly.

Comment 3

[Gregor Wagner [:gwagner]]

Do we start a new process for the settings?

Comment 4

[Dale Harvey (:daleharvey)]

We open an activity which is gonna start a new process

I think all of these bugs come under the general fix of 'assume background tabs can crash and reload when they come into the foreground' instead of the current behaviour of displaying them to the user (foreground tabs crashing will still be shown to the user)

https://bugzilla.mozilla.org/show_bug.cgi?id=998118
https://bugzilla.mozilla.org/show_bug.cgi?id=991547

are pretty much the same, should get a PR up for it tonight

Comment 5

[Gregor Wagner [:gwagner]]

Yeah not much we can do here. Either share the process or we can always come up with an example where the page gets killed.

Comment 6

[Dale Harvey (:daleharvey)]

Sorry got a little confused by the steps to reproduce, I assumed it means go to the settings app (via the offline error page)

We dont spin a new process for the in browser settings, however on a low memory device pretty much any activitey can oom a background tab (we setvisible(false) if its not in the foreground).

The fix for https://bugzilla.mozilla.org/show_bug.cgi?id=991547 also applied here

Comment 7

[Joe Cheng [:jcheng] (please needinfo)]

hi Dale, should we dup this bug to bug 991547? thanks

Comment 8

[Dale Harvey (:daleharvey)]

As the other one has landed, yup