1916146 - [WebGPU] Demo at https://play.spacelancers.com/ does not load in Firefox

Status: RESOLVED DUPLICATE of bug 1940019

(Core :: Graphics: WebGPU, defect)

Description

[Mayank Bansal]

Error:

11:17:08.336 Unknown property ‘font-color’. Declaration dropped. play.spacelancers.com:36:24
Elements matching selector: .powered-by-simplystream
NodeList [ div.powered-by-simplystream
]
11:17:08.343 Only dxt texture format available play.spacelancers.com:457:11
11:17:08.584 capabilities
Object { webgl: true, webgpu: true, offscreenCanvas: true, sharedArrayBuffer: true, webRTC: true, h264: true, vp9: true, av1: false, webTransport: true, webCodecs: true, … }
​
av1: false
​
bench_cpu: 216241
​
bench_gpu: 510541
​
h264: true
​
memory_cpu: 8589934592n
​
memory_gpu: 1000000
​
offscreenCanvas: true
​
sharedArrayBuffer: true
​
vp9: true
​
webCodecs: true
​
webRTC: true
​
webTransport: true
​
webgl: true
​
webgpu: true
​
<prototype>: Object { … }
play.spacelancers.com:1447:17
11:17:08.595 Uncaught (in promise) TypeError: BigInt value can't be serialized in JSON
<anonymous> https://play.spacelancers.com/:1448
play.spacelancers.com:1448:51
11:17:08.595 not focusing on iframe 20 play.spacelancers.com:1717:17

Comment 1

[Erich Gubler [:ErichDonGubler] (he/him)]

I'm not yet persuaded that, as described, this specific page exhibits a bug in WebGPU or Firefox. The only apparent error is about serializing a BigInt, in the console log as follows:

10:13:57.002 Uncaught (in promise) TypeError: BigInt value can't be serialized in JSON
    <anonymous> https://play.spacelancers.com/:1448
    async* https://play.spacelancers.com/:1536
play.spacelancers.com:1448:51

In latest mozilla-central, this error is generated at js/src/builtin/JSON.cpp:788-789, the behavior of which is governed by standard SerializeJSONProperty behavior in ECMA-262 v14.0, section 25.5.2.2, step 10:

10. If value is a BigInt, throw a TypeError exception.

This may be a place where Chromium is incorrectly allowing users to do this, which would be a WebCompat issue.

I'm confident that there will be other Firefox-specific issues that prevent this specific page's usage of WebGPU from working as expected (because we have a lot of stuff to do still to make our implementation usable), and I look forward to figuring those out, i.e., bug 1916145. But this bug does not seem to be that, yet.