1214376 - Rapidly-reloading about:remote-newtab triggers "Corrupted Content Error"

Status: VERIFIED FIXED

(Firefox :: New Tab Page, defect)

Description

[Daniel Holbert [:dholbert]]

STR:
 1. In Nightly with a fresh profile, visit about:remote-newtab
 2. Reload twice back to back, very quickly. (Hold Ctrl, and press R several times in rapid succession.)

ACTUAL RESULTS: A good fraction of the time, I end up at an error page:
===
Corrupted Content Error

The page you are trying to view cannot be shown because an error in the data transmission was detected.

The page you are trying to view cannot be shown because an error in the data transmission was detected.

    Please contact the website owners to inform them of this problem.
===

EXPECTED RESULTS: No such error page.

Comment 1

[Daniel Holbert [:dholbert]]

Attachment: screencast of me pressing & holding Ctrl+R for a few seconds

Here's a screencast. Note that we first go to the text-only rendering that I filed bug 1214374 about. But then we end up at the "Corrupted Content Error" page.

Comment 2

[Daniel Holbert [:dholbert]]

Nightly version: 44.0a1 (2015-10-13)

Also: once I've triggered this bug, successive reloads (whether rapid or normal) *continue* to trigger this error page. I can't get the correct about:remote-newtab rendering back unless I do "History | Clear Recent History".

Also: I see this in my error console when I trigger this error page (and on each successive reload that triggers this error page):
> ServiceWorker passed a rejected Promise to FetchEvent.respondWith().
>  This typically means that the code that resolves the Promise has failed.       about:blank

Comment 3

[Daniel Holbert [:dholbert]]

(In reply to Daniel Holbert [:dholbert] (less responsive Oct 9-12 & 15-18) from comment #2)
> Nightly version: 44.0a1 (2015-10-13)
> 
> Also: once I've triggered this bug, successive reloads (whether rapid or
> normal) *continue* to trigger this error page. I can't get the correct
> about:remote-newtab rendering back unless I do "History | Clear Recent
> History".

(One other way for me to restore the correct rendering: I can visit about:serviceworkers and click the "unregister" button. Then, my next reload on about:remote-newtab will be correct.)

Comment 4

[Olivier Yiptong [:oyiptong]]

we are aware of the issue and will be fixing it in an upcoming patch

Comment 6

[Olivier Yiptong [:oyiptong]]

This is a bug with how we are caching requests in the service worker.

That issue is fixed elsewhere and will be deployed to our CDN soon, with the url updated in nightly soon.

Comment 7

[Olivier Yiptong [:oyiptong]]

This is now fixed.

It may require going to about:serviceworkers and unregistering for origin https://newtab.cdn.mozilla.net

Comment 8

[Daniel Holbert [:dholbert]]

Thanks! I tried to reproduce this in a fresh profile, & could not cause any trouble. Marking as Verified.