Closed Bug 1280413 Opened 9 years ago Closed 9 years ago

"Corrupted Content Error" shown when reloading http://paul.kinlan.me/

Categories

(Core :: DOM: Service Workers, defect, P2)

45 Branch
defect

Tracking

()

RESOLVED DUPLICATE of bug 1263304

People

(Reporter: jhorak, Unassigned)

References

Details

Reproduction steps: 1. Go to http://paul.kinlan.me/ 2. Reload page 3. The "Corrupted Content Error" page is shown: The page you are trying to view cannot be shown because an error in the data transmission was detected. When reloading the page with Ctrl-Shift-R (cache bypass) the page reloads successfully. The error is somehow related to the service workers, there's section: <script> navigator.serviceWorker.register('/sw.js') .then(function(registration) { }, function(e) { console.log("Service Worker Failure", e); }); </script> During reloading the following message is shown in Error Console: 13:02:45.097 Failed to load 'https://paul.kinlan.me/'. A ServiceWorker passed a promise to FetchEvent.respondWith() that rejected with 'InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable'.1 sw.js:17:0
I've already contacted Paul about this. His blog is using a waitUntil() asynchronously. Neither chrome nor Firefox implement this yet. He gets away with it on chrome, though because of: https://bugs.chromium.org/p/chromium/issues/detail?id=601095 I'll dig up the bug to implement async waitUntil().
I'm going to dupe this to bug 1263304 since this is just a symptom of that. Feel free to disagree with me :)
Status: NEW → RESOLVED
Closed: 9 years ago
Priority: -- → P2
Resolution: --- → DUPLICATE
Paul has also fixed his blog.
You need to log in before you can comment on or make changes to this bug.