1258580 - Initial page fails to load from cache if Firefox is cold started

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: General, defect)

Description

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

STR:
1) Load page in Firefox
2) Recent apps -> swipe-close OOM Firefox
3) Enable airplane mode
4) Open Firefox

Expected: page loads from cache
Actual: Server not found page

I'm guessing opening the browser attempts to reload the initial page before it can load from cache since clicking on other open tabs correctly loads them from cache.

I think I've seen the same behavior when the page load is interrupted (e.g. connection is dropped). 

Also, should clicking "Try again" in the Server Not Found page load from cache?

Comment 1

[:Margaret Leibovic]

(In reply to Michael Comella (:mcomella) from comment #0)
> STR:
> 1) Load page in Firefox
> 2) Recent apps -> swipe-close OOM Firefox
> 3) Enable airplane mode
> 4) Open Firefox
> 
> Expected: page loads from cache
> Actual: Server not found page
> 
> I'm guessing opening the browser attempts to reload the initial page before
> it can load from cache since clicking on other open tabs correctly loads
> them from cache.
> 
> I think I've seen the same behavior when the page load is interrupted (e.g.
> connection is dropped). 

Does this happen with all URLs? Does loading from the cache work for the same URLs if they're in background tabs?

It sounds like something weird is happening with session restore here.

> Also, should clicking "Try again" in the Server Not Found page load from
> cache?

This sounds like another bug we should file.

Tracking this bug for 47 to figure out how hard it would be to fix this.

Comment 2

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

(In reply to :Margaret Leibovic from comment #1)
> Does this happen with all URLs?

I didn't retest but afaict.

> Does loading from the cache work for the
> same URLs if they're in background tabs?

I didn't retest but afaict.

> > Also, should clicking "Try again" in the Server Not Found page load from
> > cache?

I'd expect us never to hit "Try again" if we have it in the cache.

> This sounds like another bug we should file.

It's possible we hit "Try again" because we don't actually have it in the cache anymore – I think the investigation in this bug should clear things up more.

Comment 3

[:Grisha Kruglov]

I don't see this happening on nightly anymore. Work that landed to un-bug offline caching seems to have fixed this as well.