Because you are using Torch and I assume a fairly large model, what is likely happening is that you are running out of RAM. This will crash the container the app is running in, and the browser will try to connect to the healthz endpoint but not get a response.
There isn’t a great solution right now, as we try and understand users usage patterns on Streamlit sharing during this beta period. It’s likely the case that your app needs 2-4x the resources we allocate, and maybe even more. That’s hard for us to sustain as a free service, but we’re trying to figure out ways to make this use case work in a cost-effective manner for us.
Thanks for stopping by! We use cookies to help us understand how you interact with our website.
By clicking “Accept all”, you consent to our use of cookies. For more information, please see our privacy policy.
Cookie settings
Strictly necessary cookies
These cookies are necessary for the website to function and cannot be switched off. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms.
Performance cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us understand how visitors move around the site and which pages are most frequently visited.
Functional cookies
These cookies are used to record your choices and settings, maintain your preferences over time and recognize you when you return to our website. These cookies help us to personalize our content for you and remember your preferences.
Targeting cookies
These cookies may be deployed to our site by our advertising partners to build a profile of your interest and provide you with content that is relevant to you, including showing you relevant ads on other websites.