1814976 - Google doc shows error with constant reload

Status: RESOLVED WORKSFORME

(Core :: Graphics, defect, P2)

Description

[Mike Conca [:mconca]]

Attachment: Modal error dialog presented by Google Docs

When any open Google Doc is left open and unused in a tab for multiple days, it eventually ends up in a state where the content is greyed out (or sometimes missing), the tab shows the "throbber" indicating it is trying to load, and there is an alert() modal dialog over the page stating:

"This error has been reported to Google and we'll look into it as soon as possible. Please reload this page to continue." (see image)

Reloading the page does indeed seem to restore it to normal. No exact steps to reproduce, other than load a doc and leave it in a tab for many days. Doesn't seem to impact Google Sheets or Slides, only Docs. I've seen it on pinned and unpinned tabs.

Comment 1

[Mike Conca [:mconca]]

I reached out to Google about this. Their response indicated that, yes, they are seeing an increased error rate since the rollout of Firefox 109. The top error they are seeing is thrown when calling context.scale on an HTML canvas. The same error can be induced by making a very large canvas.

Did anything change with canvas in Firefox 109? (pinging some graphics folks)

Comment 2

[Jim Mathies [:jimm]]

What platform are we seeing this on, MacOS?

Comment 3

[Neha Kochar [:neha]]

I have experienced this too recently. I'm using MacOS.

Comment 4

[James Graham [:jgraham]]

Not just macOS, I also see this on Linux.

Comment 5

[Mike Conca [:mconca]]

Windows 11 for me

Comment 6

[Bob Hood [:bhood]]

This feels like a network timeout/disconnect to me, with reloading the page causing a re-connect to Google's cloud servers. Miro does this as well with a shorter timeout, but handles it much more gracefully. It just reconnects as soon as the tab comes into focus again.

I see it started in Networking. Was it proven there that no timeout/disconnect was actually occurring?

Comment 7

[Randell Jesup [:jesup] (needinfo me)]

I imagine they're using a WebSocket or other such mechanism to keep an open Doc synced with the clowd, displaying who has it open, etc. If that connection dies and they fail to properly re-establish it, that might cause this sort of error. Just a guess

Comment 8

[Florian Quèze [:florian]]

(In reply to Bob Hood [:bhood] from comment #6)

This feels like a network timeout/disconnect to me, with reloading the page causing a re-connect to Google's cloud servers.

If there's a networking issue, could it be bug 1814961?

I see it started in Networking. Was it proven there that no timeout/disconnect was actually occurring?

"The top error they are seeing is thrown when calling context.scale on an HTML canvas." from comment 1 sounded like it was not (only) a network issue. Or are you suggesting some of the page's JS code could be misbehaving after a timeout and cause the canvas to error because of bad input?

Comment 9

[Bob Hood [:bhood]]

Or are you suggesting some of the page's JS code could be misbehaving after a timeout and cause the canvas to error because of bad input?

That hadn't occurred to me, but definitely sounds plausible.

Comment 10

[Mike Conca [:mconca]]

Not sure if Google fixed something on their end, but I haven't seen this for about a week now.

Comment 11

[Henrik Skupin [:whimboo][⌚️UTC+1]]

(In reply to Florian Quèze [:florian] from comment #8)

(In reply to Bob Hood [:bhood] from comment #6)

This feels like a network timeout/disconnect to me, with reloading the page causing a re-connect to Google's cloud servers.

If there's a networking issue, could it be bug 1814961?

Please note that the patch on bug 1814961 has landed today and is now in the Firefox Nightly.

Comment 12

[Ashley Hale [:ahale]]

Reporter says the bug stopped happening, closing.