web page crashes on older Galaxy devices loading duckdb shell

[cfahlgren1]

What happens?

On older mobile devices, opening the DuckDB WASM Shell will crash the page.

I am not totally sure if the issue is Memory, OS, or the Browser, but seems to be happening on mobile devices with less than 3GB memory. Could it be because DuckDB WASM wants to the typical 4GB memory and OS / Browser kills the page?

Would love to know ways to detect this or if there was an ability to fail gracefully.

To Reproduce

User mentioned having this issue on Galaxy A03, Chrome 99, Android 12, 1GB RAM.

I was able to reproduce on this device. (It works for iPhones and other similar devices fwiw)

Galaxy Tab Lite

Specification	Details
Memory	3 GB
OS	Android 11

Browser/Environment:

Chrome 99

Device:

Galaxy Tab Lite

DuckDB-Wasm Version:

v1.1.0

DuckDB-Wasm Deployment:

shell.duckdb.org

Full Name:

Caleb Fahlgren

Affiliation:

Hugging Face

[carlopi]

Hi, thanks for raising this.

This should definitively not crash, what we are missing is at the moment some proper way to test this scenario.
I don't think it's connected to the memory limit, possibly to WebWorker availability, but I need to figure out what's the proper way to handle this, both in the specific and generic case.