STR: 1. In Nightly, visit https://drive.google.com/drive/u/0/ ER: The page eventually finishes loading. AR: This, forever: https://screenshotscdn.firefoxusercontent.com/images/50c49745-7139-4a81-9534-4df2dc0e5304.png I used mozregression, and apparently bug 1456604 caused this.

Sounds like a blocker to me.

To be clear, this was the changeset range that mozregression spewed out: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=3ee25bda924ea97cbda2d8602ede83b30c61eb19&tochange=7b6f6fcaaa177324d1827f9be431e23e9e0573ad But that other commit is a comment-only change. Hey sfink, given the regressing changeset, are there any diagnostic steps I could run to help figure out what's going on here?

My money would be on this being a dupe of bug 1458320 (and yes, this is from bug 1456604). Do you get anything in the console?

(I can't reproduce with my nightly, but perhaps it depends on having written something into IndexedDB with the "right" Nightly.)

(In reply to Steve Fink [:sfink] [:s:] (PTO June 31) from comment #3) > My money would be on this being a dupe of bug 1458320 (and yes, this is from > bug 1456604). Do you get anything in the console? Only when I access the IndexedDB data for the page via the DevTools - I get: "bad serialized structured data (incompatible structured clone scope)" So plausibly this is a dupe of bug 1458320 (which is reporting a similar error message). Let's wire up a dependency and see if this gets fixed once bug 1458320 gets fixed.

Experiencing a similar issue with google docs.

This is making it so I cannot use Nightly to do my work.

There's a patch on inbound now which will hopefully resolve this. Aim is to get it merged to m-c in time for this afternoon's nightly builds.

I just updated to the second Nightly of the day and https://drive.google.com works again for me.

Just updated to 20180502220059, and this appears to be working for me now. Gonna dupe this over.

Yay! All is good again. Thanks!