Playground crashed error report

[ruchirg]

Playground crashed because of an error. You can help resolve the issue by sharing the error details with us.

[10-Oct-2025 09:24:27 UTC] JavaScript error: Failed to fetch
TypeError: Failed to fetch

https://playground.wordpress.net/?blueprint-url=https%3A%2F%2Fwordpress.org%2Fthemes%2Fwp-json%2Fthemes%2Fv1%2Freview-blueprint%2F71106-chronocards-ruchir%2F1.1&modal=error-report

This is the URL i try to access
https://playground.wordpress.net/?blueprint-url=https%3A%2F%2Fwordpress.org%2Fthemes%2Fwp-json%2Fthemes%2Fv1%2Freview-blueprint%2F71106-chronocards-ruchir%2F1.1&modal=error-report

[adamziel]

Thanks for the report @ruchirg! That's a good opportunity to brush up error reporting – the site should explain exactly which fetch failed instead of showing a general error moda.

[adamziel]

By a peculiar coincidence, I've just ran into the same error. Turns out, I was running low on disk space and Chrome refused to serve the request to download WordPress.zip. I've cleaned up some space and now I can see this:

I see reports of a similar problem in axios/axios#6358. The error is weird in that chrome doesn't even tell us which request failed or why. I don't see any way we can report a more useful error here — I'm happy to revisit it if anyone has an idea.

@ruchirg can you confirm the disk space was indeed an issue for you? And, if not, would updating the browser, restarting, etc. help? I don't think "Failed to fetch" without any stacktrace involved is related to anything Playground is doing.

[adamziel]

I'll add that I found the request fails only by stepping through the execution and realizing which line causes problems. Then, I confirmed pasting this in devtools failed:

(await fetch('/@fs/Adam/wordpress-playground/packages/playground/wordpress-builds/src/wordpress/wp-6.8.zip')).blob()

The failure mode was interesting, too. The network panel showed a new request that said 200 ERR_FAILED.

Interestingly, it still worked in incognito mode.

My read is it's either the disk space, the service worker storage quota, or both interacting together.

[ruchirg]

this is the video refrance that issuew have in chrome it work in firefox and other browser my chrome version is Version 141.0.7390.54 (Official Build) (64-bit)
https://github.com/user-attachments/assets/218ae5f0-dc2a-4b13-821b-0bb58c80b760

[adamziel]

@ruchirg thank you for the video! Unfortunately I don't be of much help without these data points I've asked for above:

@ruchirg can you confirm the disk space was indeed an issue for you? And, if not, would updating the browser, restarting the computer, etc. help?

[ruchirg]

@ruchirg thank you for the video! Unfortunately I don't be of much help without these data points I've asked for above:

@ruchirg can you confirm the disk space was indeed an issue for you? And, if not, would updating the browser, restarting the computer, etc. help?
I have plenty of disk space, and the issue does not occur in Firefox. The “Failed to fetch” error still appears in Chrome despite using the latest version and restarting the browser.
and error is generate very early at the starting point.

[adamziel]

Thank you for confirming @ruchirg? Is there anything different at all about your Chrome setup? Such as an enterprise profile, firewall rules, different proxy setup, ad blockers etc? Does that Blueprint work in private mode? If yes, that's a good indication it's related to some extension or a configuration option. If not, let's keep discussing.

[ruchirg]

Hello @adamziel Here is the screenshot of the error I found in the console.

[adamziel]

@ruchirg Thank you! It confirms what I've suspected – fetch fails without the browser giving any error details, which means it's not actually related to the server response. Your answers to the questions from my last comment will help us move forward here.