1636034 - github.io/hectic-rs-wasm game not loading on Windows 10

Status: NEW

(Web Compatibility :: Desktop, defect, P2)

Description

[Cristian Fogel, QA [:cfogel]]

Attachment: adsd (2).txt

Note

• filed as follow up for bug 1634239;

Affected versions

• 77.0b2, 78.0a1(2020.05.05);

Affected platforms

• Windows 10;

Steps to reproduce

1. Launch Firefox and enable "dom.webgpu.enabled" and "gfx.webrender.all", "gfx.webrender.enabled" then restart;
2. open "https://expenses.github.io/hectic-rs-wasm/"
3. play for about 1-5 minutes. It was reported to crash at ~15 seconds mark, depends on the JS garbage collector

Expected result

• game loads and is playable;

Actual result

• game does not load on Windows;
• in one case after a page refresh tab(not browser) crashed;

Regression range

• will check asap;

Additional notes

• attached log from the console;
• disabled tracking protection but the same result.

Comment 1

[abodenlosz]

Regression range:

• Wasn't able to find a regression. I went back as far as Nightly 45.0a1 and the issue was still reproducible.

Comment 2

[Jessie [:jbonisteel] pls NI]

Is this really a WebGPU bug? According to comment 1, this has been happening as far back as 45...

Comment 3

[Dzmitry Malyshau [:kvark]]

This web page is definitely using WebGPU. I just loaded it in Chrome and observed this in the console (and the page doesn't work, since I didn't enable WebGPU in Chrome):

hectic-rs.js:343 panicked at 'expected to get context from canvas', /home/ashley/.cargo/git/checkouts/wgpu-rs-40ea39809c03c5d8/f79ee51/src/backend/web.rs:626:18

This bug is about NS_ERROR_FILE_UNRECOGNIZED_PATH, which has nothing to do with WebGPU... I don't know much about the JS call stack provided, so I guess moving it to "General" is the way to have somebody more relevant to take a look. Might as well be just a broken page, or a WebCompat issue.

:cfogel - would be good to update the repro steps here, these were copied over from the WebGPU bug 1634239. Since this isn't related to WebGPU, (1) and (3) repro steps given are incorrect.

Comment 4

[Nhi Nguyen (:nhi)]

Moving to WebCompat for the folks there to take a look. Feel free to move it back if it isn't a webcompat issue.

Comment 5

[Oana Arbuzov [:oanaarbuzov]]

I was able to reproduce the tab crash every time.
https://prnt.sc/yextjc

Tested with:
Browser / Version: Firefox Nightly 87.0a1 (2021-02-04)
Operating System: Windows 10 Pro