svelte
svelte copied to clipboard
Svelte code with many function calls crashes on Webkit
Describe the bug
If there are too many calls to a function, Epiphany (Gnu Web - Webkit) browser crashes. Chrome and Firefox work ok.
I'm starting browser with cairo
renderer.
WEBKIT_DISABLE_COMPOSITING_MODE=0 EPHY_LOG_MODULES=ephy-window.c EPHY_DEBUG_BREAK=stack WEBKIT_FORCE_SANDBOX=0 GSK_RENDERER=cairo flatpak run --verbose org.gnome.Epiphany
Is there anything on Svelte side that can be done with this?
Reproduction
https://svelte.dev/repl/1ad99e89d4614ebba758feaa98859922?version=4.2.15
Logs
`(epiphany:2): epiphany-WARNING **: 17:28:51.461: Web process crashed`
System Info
System:
OS: Linux 5.4 Ubuntu 20.04.6 LTS (Focal Fossa)
CPU: (2) x64 Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz
Memory: 667.31 MB / 3.83 GB
Container: Yes
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 20.4.0 - ~/.nvm/versions/node/v20.4.0/bin/node
Yarn: 1.22.17 - /usr/local/bin/yarn
npm: 9.7.2 - ~/.nvm/versions/node/v20.4.0/bin/npm
bun: 1.0.26 - ~/.bun/bin/bun
Watchman: 20201115.021953.0 - /usr/local/bin/watchman
Browsers:
Gnome Web (Epiphany) 46.0 - Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.0 Safari/605.1.15
npmPackages:
svelte: ^4.2.12 => 4.2.12
Severity
blocking all usage of svelte
This works on Safari on MacOS. It sounds like this might be an Epiphany specific bug?
Couldn't reproduce on Epiphany 46 / Debian or any other brother. Most likely setup related, try without rendering/logging options or without flatpack.
This works on Safari on MacOS. It sounds like this might be an Epiphany specific bug?
Thank you for checking. I assumed that WebKit is same in both. Might be something with this browser and my OS.
Couldn't reproduce on Epiphany 46 / Debian or any other brother. Most likely setup related, try without rendering/logging options or without flatpack.
The stand alone version is 3.36.4 on Ubuntu 20 and it crashed. Same for Epiphany Canary via flatpak.
Flatpak without cairo
renderer can't be run b/c of OpenGl and NVIDIA driver conflicts.
So it seems it has to be a problem with old OS and/or drivers.