Segmentation fault on Community Cloud — even happens with the default/starter template, not just my app

Community Cloud
,
1

Key finding: this is not specific to my app

I also deployed Streamlit’s own default/starter template app (no custom code, no extra dependencies) on the same Community Cloud account, and it fails with the exact same segmentation fault. This strongly suggests the problem is not in my app’s code or dependencies, but something at the account/workspace or platform level on my end of Community Cloud.

Given that, I’d really appreciate help figuring out whether this is a known account/workspace-level issue rather than continuing to debug my specific app’s dependencies.

1. Public app link

https://titaniceda-yxjxoxd6hbt6uffamktk3t.streamlit.app/

2. GitHub repository

GitHub - Donggyu-Hwang/titanic_eda · GitHub (branch: main, main module: streamlit_app.py)

3. Full error message

The app fails the health check and crashes with a segfault every time, shortly after dependencies finish installing. No Python traceback is ever printed — the process just dies.

[05:25:16] 📦 Processed dependencies!

[05:30:04] ❗️ The service has encountered an error while checking the health of the Streamlit app: Get "http://localhost:8501/script-health-check": EOF
/app/scripts/run-streamlit.sh: line 9:   262 Segmentation fault      sudo -E -u appuser /home/adminuser/venv/bin/streamlit "$@"
  1. Since even the default template crashes on my account, is this a known account/workspace-level issue? Is there something specific to check or reset (e.g., re-linking GitHub, workspace region, a corrupted build cache)?
  2. Is there a way to get more detailed crash output (e.g., a core dump or native stack trace) from Community Cloud rather than just “Segmentation fault”?
  3. Has anyone else seen the default template itself segfault on Community Cloud?

Happy to share the full repo, the default-template repro repo, or any additional logs. Thanks in advance!

2

Welcome to the Streamlit community and thanks for your detailed report! :blush: If even the default Streamlit template segfaults on your Community Cloud account, it seems likely this is a platform-level or account/workspace-level issue, not a problem with your app code or dependencies. Segmentation faults right after dependency installation, with no Python traceback, are not typical for user code errors and have been reported in rare cases when there are resource exhaustion issues, platform bugs, or account-level blocks on Community Cloud. There’s no documented way to get a core dump or native stack trace from Community Cloud—logs are limited to what’s shown in the Cloud dashboard and deployment logs.

My understanding is that known causes for this include: (1) exceeding resource limits (CPU, RAM, storage), (2) hitting fair-use or abuse blocks at the account level, or (3) a corrupted workspace or environment on the backend. If you see segmentation faults even with the default template, and especially if you’ve already tried rebooting, deleting/redeploying, and using a fresh repo, it’s likely not fixable from your side. The best next step is to contact Streamlit support directly and reference your account and app URLs, as they can check for backend issues, workspace corruption, or account blocks. For more on resource limits and troubleshooting, see the official docs and related forum threads. Community members, please jump in if you’ve seen similar issues or have additional insights!

Sources:

3

This is most likely be caused by a bug in pyarrow 25.0.0: [C++][Python] SIGSEGV in bundled mimalloc mi_thread_init when libarrow is first loaded on a non-main thread that exits (mimalloc 3.3.x, pyarrow 25.0.0) · Issue #50471 · apache/arrow · GitHub
Please make sure to update to Streamlit 1.59.2 or pin pyarrow < 25.0.0 to prevent this crash.