Open Bug 1933645 Opened 4 months ago Updated 2 months ago

Categories

(Core :: Graphics: WebGPU, defect)

defect

Tracking

()

Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox133 --- disabled
firefox134 --- disabled
firefox135 --- disabled

People

(Reporter: mayankleoboy1, Unassigned)

References

(Blocks 1 open bug, Regression, )

Details

(Keywords: regression)

Attachments

(1 file)

Go to https://www.fxhash.xyz/generative/slug/adroste
Click Run

AR: Nothing is drawn on screen
ER: It should, like Chrome

Errors:
11:59:32.191 missing RESERVOIR_API_KEY 2314-ad452e0873d4fb9e.js:1:228314
11:59:32.332 artworkArtifactUrl undefined 1136-08e259f109992cab.js:1:8968
11:59:32.493 No wallet connected, clearing user state 2314-ad452e0873d4fb9e.js:1:29769
11:59:32.493 clearing user state disconnect true
Object { TEZOS: null, ETHEREUM: null }
2314-ad452e0873d4fb9e.js:1:28557
11:59:32.533 injected firefox content.js:142:11
11:59:33.354 Content-Security-Policy: The page’s settings blocked the loading of a resource (frame-src) at https://verify.walletconnect.org/111994543d1b754bab82c368d0e61ae5 because it violates the following directive: “frame-src https://gateway.fxhash2.xyz https://file-api.fxhash.xyz https://onchfs.fxhash2.xyz https://challenges.cloudflare.com https://.spotify.com/ https://spotify.com https://.youtube.com/ https://youtube.com https://*.twitter.com/ https://twitter.com https://codepen.io https://openprocessing.org https://checkout.usewinter.com/ https://widget.wert.io https://centinelapi.cardinalcommerce.com https://player.vimeo.com https://verify.walletconnect.com/ https://ghostnet.kukai.app/ https://wallet.kukai.app/ 'self'” adroste
11:59:42.739 Feature Policy: Skipping unsupported feature name “accelerometer”. framework-1c4219c70bd44fc5.js:1:3401
11:59:42.739 Feature Policy: Skipping unsupported feature name “gyroscope”. framework-1c4219c70bd44fc5.js:1:3401
11:59:42.739 Feature Policy: Skipping unsupported feature name “xr-spatial-tracking”. framework-1c4219c70bd44fc5.js:1:3401
11:59:42.740 Feature Policy: Skipping unsupported feature name “accelerometer”. framework-1c4219c70bd44fc5.js:1:95098
11:59:42.740 Feature Policy: Skipping unsupported feature name “gyroscope”. framework-1c4219c70bd44fc5.js:1:95098
11:59:42.740 Feature Policy: Skipping unsupported feature name “xr-spatial-tracking”. framework-1c4219c70bd44fc5.js:1:95098
12:04:08.905 Feature Policy: Skipping unsupported feature name “accelerometer”. framework-1c4219c70bd44fc5.js:1:3401
12:04:08.905 Feature Policy: Skipping unsupported feature name “gyroscope”. framework-1c4219c70bd44fc5.js:1:3401
12:04:08.905 Feature Policy: Skipping unsupported feature name “xr-spatial-tracking”. framework-1c4219c70bd44fc5.js:1:3401
12:04:08.906 Feature Policy: Skipping unsupported feature name “accelerometer”. framework-1c4219c70bd44fc5.js:1:95098
12:04:08.906 Feature Policy: Skipping unsupported feature name “gyroscope”. framework-1c4219c70bd44fc5.js:1:95098
12:04:08.906 Feature Policy: Skipping unsupported feature name “xr-spatial-tracking”. framework-1c4219c70bd44fc5.js:1:95098
12:04:09.093 Content-Security-Policy: Couldn’t process unknown directive ‘prefetch-src’ QmccmgxuEkZgrUKYEUBfwjkfv1UQLn4vGrgGd4LmerhQ7P
12:04:09.139 Partitioned cookie or storage access was provided to “https://gateway.fxhash2.xyz/ipfs/QmccmgxuEkZgrUKYEUBfwjkfv1UQLn4vGrgGd4LmerhQ7P/?fxhash=ooLJcUgWzMN6RXUwQ7SagVDkTS9pM2gMADVocEj2Jf3FBBASpXP&fxchain=TEZOS&fxiteration=1&fxminter=tz1xHF6DJ7pWKTJF8UWzNRK5daYR5daFYW4u&fxparamsUpdate=28fe28b44004d717543d30a5b811fe01a69be69e#0x0140fca67000000000ff0000ff00ff00ff0000ffff000000ff01004014000000000000400800000000000040fd74c000000000014103c3d0000000004112e5cc0000000040000000000000004008000000000000” because it is loaded in the third-party context and dynamic state partitioning is enabled.

12:04:09.184
Uncaught Error: Using exceptions for control flow, don't mind me. This isn't actually an error!
_0x140e3e https://gateway.fxhash2.xyz/ipfs/QmccmgxuEkZgrUKYEUBfwjkfv1UQLn4vGrgGd4LmerhQ7P/748.js:1
__wbindgen_throw https://gateway.fxhash2.xyz/ipfs/QmccmgxuEkZgrUKYEUBfwjkfv1UQLn4vGrgGd4LmerhQ7P/index.js:1
_0x5ad1c8 https://gateway.fxhash2.xyz/ipfs/QmccmgxuEkZgrUKYEUBfwjkfv1UQLn4vGrgGd4LmerhQ7P/748.js:1
_0x56cdcf https://gateway.fxhash2.xyz/ipfs/QmccmgxuEkZgrUKYEUBfwjkfv1UQLn4vGrgGd4LmerhQ7P/748.js:1
748.js:1:242976
12:04:09.232
Uncaught RuntimeError: unreachable executed
_0x5ad1c8 https://gateway.fxhash2.xyz/ipfs/QmccmgxuEkZgrUKYEUBfwjkfv1UQLn4vGrgGd4LmerhQ7P/748.js:1
_0x56cdcf https://gateway.fxhash2.xyz/ipfs/QmccmgxuEkZgrUKYEUBfwjkfv1UQLn4vGrgGd4LmerhQ7P/748.js:1
index.js line 1 > WebAssembly.instantiate:2390589:1
12:04:11.053
Unknown property ‘-moz-osx-font-smoothing’. Declaration dropped. adroste:5:328
12:04:11.065
Unknown property ‘-moz-osx-font-smoothing’. Declaration dropped. QmccmgxuEkZgrUKYEUBfwjkfv1UQLn4vGrgGd4LmerhQ7P:126:29
12:04:11.086 Ruleset ignored due to bad selector. 8c775f061f1b8cd8.css:1:4335
12:04:11.086 Ruleset ignored due to bad selector. 8c775f061f1b8cd8.css:1:4401
12:04:11.086
Unknown property ‘speak’. Declaration dropped. 8c775f061f1b8cd8.css:1:5628
12:04:11.086
Unknown property ‘-moz-osx-font-smoothing’. Declaration dropped. 8c775f061f1b8cd8.css:1:5810
12:04:11.371 Source map error: Error: URL constructor: is not a valid URL.
Stack in the worker:resolveSourceMapURL@resource://devtools/client/shared/source-map-loader/utils/fetchSourceMap.js:56:22
getOriginalURLs@resource://devtools/client/shared/source-map-loader/source-map.js:73:24
workerHandler/</<@resource://devtools/client/shared/worker-utils.js:115:52
workerHandler/<@resource://devtools/client/shared/worker-utils.js:113:13

Resource URL: wasm:https://gateway.fxhash2.xyz/ipfs/QmccmgxuEkZgrUKYEUBfwjkfv1UQLn4vGrgGd4LmerhQ7P/index.js%20line%201%20%3E%20WebAssembly.instantiate
Source Map URL: null

Attached file about:support

tested on other modern web browsers (Chrome, Firefox, Safari, Edge)

It does work for me on Firefox release. Mayank, can you use mozregression to find out if this is a (recent) regression?

Flags: needinfo?(mayankleoboy1)

This is the regression range: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=45fc9bb4de9c9d7d5b9933977891a99d10e47d6e&tochange=9754c55103ef774188e1e813a3ef5d4f5487b35c

There may be more than one bug here. In some builds i tried, the demo used CPU/GPU but nothing was drawn on the screen. In latest Nightly, cpu use also stops after few seconds.

This may not be a JS/wasm bug, and may be a gfx bug. No idea.

Flags: needinfo?(mayankleoboy1)

Thanks!

That's mysterious, the regression range goes back to March 2023 but the demo works for me with Firefox 133.0 The regression range has "Enable WebGPU in Nightly" in it and the website says it uses WebGPU so it's likely related to that change.

Profile with webgpu logging preset: https://share.firefox.dev/4fQFzR2

Bisection:

Bug 1919404 - chore(webgpu): remove stale maxInterStageShaderComponents.as_worker.js CTS file
Discovered and remedied alongside
this comment of mine in
gpuweb/cts#3834
.
😅
Differential Revision: https://phabricator.services.mozilla.com/D223978


Prior to bisection: Nothing is drawn on the screen. Demo uses 1GB RAM nad continues to use CPU. If you try to capture a profile, the profiler will hang
Post bisection: The CPU use stops almost immediately.

Component: JavaScript: WebAssembly → Graphics: WebGPU
Keywords: regression
Regressed by: 1919404

Set release status flags based on info from the regressing bug 1919404

:ErichDonGubler, since you are the author of the regressor, bug 1919404, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Blocks: webgpu-apps
Severity: -- → S3
Flags: needinfo?(egubler)

It's difficult to tell if something is going wrong specifically with WebGPU, since there are no relevant console errors that I can see. If this truly is a regression from bug 1919404, then it seems like the WASM blob backing the website needs to be rebuilt on IDL that does not contain GPUSupportedLimits.maxInterStageShaderComponents.

I'm not even sure how this page is targeting WebGPU with WASM, but I suspect it is built in Rust, using WGPU's wasm32-unknown-unknown target. If so, they need to consume the latest release of WGPU, which fixes this issue.

If I force disable webgpu from about:config, the demo runs (falling back to webgl i guess) : https://share.firefox.dev/3Vf4xkz

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: