Bug 264487 - svelte.dev tutorial page frequently shows "Yikes! We couldn't start the app"
Summary: svelte.dev tutorial page frequently shows "Yikes! We couldn't start the app"
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: Safari Technology Preview
Hardware: Mac (Apple Silicon) macOS 14
: P2 Normal
Assignee: Nobody
URL:
Keywords: BrowserCompat, InRadar
Depends on:
Blocks:
 
Reported: 2023-11-09 07:45 PST by lyz3636
Modified: 2023-11-16 07:46 PST (History)
3 users (show)

See Also:


Attachments
svelte error screenshot (439.84 KB, image/png)
2023-11-09 07:45 PST, lyz3636
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description lyz3636 2023-11-09 07:45:44 PST
Created attachment 468534 [details]
svelte error screenshot

go to: https://learn.svelte.dev/tutorial/welcome-to-svelte
sometimes in the bottom right panel, this error occurs (see attachment)
Comment 1 lyz3636 2023-11-09 07:47:18 PST
if you can't reproduce the bug, refresh the page a few times. 
i also noticed that this bug will make my battery drain faster
Comment 2 Alexey Proskuryakov 2023-11-09 15:55:22 PST
Thank you for the report! This reproduced for me with Safari 17.2 beta on the first try.

Could you please share if you have reasons to believe that this is a Safari/WebKit issue, and not a website one? E.g. does this work in other browsers, or in older Safari versions?
Comment 3 lyz3636 2023-11-09 15:56:25 PST
yes! It works just fine in firefox.
Comment 4 Karl Dubost 2023-11-09 21:46:35 PST
There is a "NULL/" CANNOT BE PARSED AS A URL.

> Yikes!
> We couldn't start the app. Please ensure third party cookies are enabled for this site.


Just before failing there is a message in the console which is not happening when this is working.

Unhandled Promise Rejection: RangeError: Out of memory
in https://w-corp.staticblitz.com/webcontainer.5a198b5c.js
It points to obfuscated code…


```
await this['_ready'];
let _0x108c38 = async (_0x4f6726, _0x14bd92, _0xb69944, _0x51215e) => {
	let _0x116f1d = await _0x2a886c(_0x4f6726, _0x14bd92, _0xb69944, _0x51215e);
	return _0x116f1d instanceof ArrayBuffer ? _0x406aed(_0x116f1d, [_0x116f1d]) : _0x116f1d;
};
return await this['_fetcherComlink']['registry']['addLazyFileHandler'](_0x1d3fc0, _0x155028(_0x108c38)) ?? (() => {});
}
```

It should be possible to de-obfuscate but let's see first how much we can do without it.

The resource https://w-corp.staticblitz.com/fetch.worker.5a198b5c.js was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it wasn't preloaded for nothing.

I got into a state in Firefox Nightly, without the error message but an incomplete state too. 
And I got the same limbo state in Chrome Canary.

So I'm not certain that this is only Safari.
but maybe it's happening more often in Safari?
Comment 5 lyz3636 2023-11-10 06:29:40 PST
I am not using Firefox Nightly, just regular Firefox. I have been refreshing to try to reproduce the error and I haven't succeeded. That's all i know. I don't know what is an incomplete state but at least i didn't see the error...
Comment 6 Radar WebKit Bug Importer 2023-11-16 07:46:14 PST
<rdar://problem/118510128>