In looking at your app, unfortunately I think this has to do with using Torch. As far as I can tell, your app doesn’t have any obvious flaws, but Torch is such a big dependency that running your app a few times then exhausts all available RAM, which causes the error you are seeing.
I’ll forward this thread on to our product and cloud teams, so they can have another example and possibly find a solution for this.
Please let me know how I can clean up my code or requirements to keep this error from popping up, or whether there are improvements that your service are due for to resolve this issue. Thanks.
I’m not using Torch, but I got the same error. Must be due to memory usage, even on my local machine it would be running very slow due to several Folium maps generating in sequence, but how to fix it?
[19:20:45] The service has encountered an error while checking the health of the Streamlit app: Get “http://localhost:8501/healthz”: read tcp 127.0.0.1:49860->127.0.0.1:8501: read: connection reset by peer
/app/scripts/run-streamlit.sh: line 9: 213 Killed sudo -E -u appuser /home/adminuser/venv/bin/streamlit “$@”
[19:22:16] Streamlit server consistently failed status checks
[19:22:16] Please fix the errors, push an update to the git repo, or reboot the app.