908455 - refresh of browser tab after OOM kill fails if refresh button pressed too quickly

Status: RESOLVED WONTFIX

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

Description

[Ben Kelly [:bkelly, not reviewing]]

Steps to reproduce:

  1) Open three browser tabs with sites that will trigger the OOM killer.  I used washingtonpost.com, cnn.com, and slashdot.org.

  2) Switch between the tabs.  Observe that when switching to a killed tab it auto-refreshes as designed.  The auto-refresh occurs after a one to two second pause on my buri device.

  3) In the short pause before the auto-refresh occurs, press the refresh button.

At this point the page resolves to a white screen.  Pressing the refresh button does not help.  Switching tabs does not help.  The tab must be closed and a new tab created to recover.

This may seem like a rare occurrence, but I think its reasonable for an impatient user to press the refresh button after switching tabs.  I did this while researching another bug today and ran into this behavior.

I've reproduced this on vendor 1.1 software, v1-train/b2g18, and master/m-c.

Comment 1

[Karen Rudnitski [:kar]]

This does need to be fixed, but I don't believe it should block due to the likely behaviour of our target users and the relatively rare frequency this type of OOM may present itself.

Comment 2

[Ben Kelly [:bkelly, not reviewing]]

(In reply to Karen Rudnitski [:kar] from comment #1)
> This does need to be fixed, but I don't believe it should block due to the
> likely behaviour of our target users and the relatively rare frequency this
> type of OOM may present itself.

I'm not arguing the koi-, but my personal experience is that OOM tab killing is very easy to trigger with normal use on my buri.

Comment 3

[Karen Rudnitski [:kar]]

Absolutely noted - hence I want it fixed, but just don't want it designated as blocking :)

Comment 4

[BMO Automation]

Firefox OS is not being worked on