[Bug]: NYTimes Crossword Mini is not loading

[fbertsch]

Steps to reproduce

1. open https://www.nytimes.com/crosswords/game/mini
2. Cannot load the page

Expected behaviour

Should open the page. Recent update changed this behavior (I think 2 days ago?)

Actual behaviour

The page doesn't load. Firefox says it can't load the page.

Device name

Samsung s10e

Android version

Android 12

Firefox release type

Firefox Nightly

Firefox version

102.0a1

Device logs

3c904807-de33-4be1-82c5-b0dd42bf9f97

Additional information

No response

┆Issue is synchronized with this Jira Task

[kbrosnan]

If possible connect desktop's devtools and check if the number output from the js console command in bug link below is in the +520k range. If so then this is bz-1755206

• https://firefox-source-docs.mozilla.org/devtools-user/about_colon_debugging/
• https://bugzilla.mozilla.org/show_bug.cgi?id=1755206#c1

[fbertsch]

@kbrosnan I managed to get debugging working. When the tab loads, it starts spitting out some JS, and the last console log is a cross-origin request error. It then completely dies on the entire tab looks like this (no logs, no nuthin'):

[fbertsch]

I also noticed that it happens on the regular crossword site as well: https://www.nytimes.com/crosswords/game/daily/2022/05/28

And is not happening on desktop.

[kbrosnan]

Would you reach out to the devtools team about how to query the storage usage in Fenix.

[fbertsch]

FYI I'm able to repro this on a Pixel 6

[jonalmeida]

I can reproduce this bug as well.

The debugger shows a white screen because the tab process is crashing. I was able to attach a debugger before it crashed, but it eventually shows the same white screen too.

In the main process, the debugger shows these errors:

Uncaught TypeError: can't access property "sendAsyncMessage", this._manager.messageManager is null
    _updateContentModuleState chrome://geckoview/content/geckoview.js:497
    set enabled chrome://geckoview/content/geckoview.js:472
    init chrome://geckoview/content/geckoview.js:115
    forEach chrome://geckoview/content/geckoview.js:150
    init chrome://geckoview/content/geckoview.js:114
    init chrome://geckoview/content/geckoview.js:113
    startup chrome://geckoview/content/geckoview.js:543
    EventListener.handleEvent* chrome://geckoview/content/geckoview.xhtml:12

This trace doesn't seem useful to me though, looks like it's just confirming the process we tried to send a message to has crashed.

I tried the page with Tracking Protection disabled - same crash.

This is on Nightly 105. Crash status link: https://crash-stats.mozilla.org/report/index/697bab28-9aa0-4564-a2a4-95c080220811

Reproduced on Reference Browser. Crash stats link: https://crash-stats.mozilla.org/report/index/a60db97c-5d40-4e7b-af5a-97fd10220811

On Beta 104, it's not crashing for me.

[csadilek]

Moved to bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1813766

Change performed by the Move to Bugzilla add-on.