You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 9, 2024. It is now read-only.
I installed the beta last week and I've been installing each update as they come so I'm up to date.
I logged in with my account and have switched organizations, but due to another bug #20 I haven't used the new app much.
I closed out of the app, but apparently the process was still running in the background, and almost 24 hours later my operating system started grinding to a halt, and when I tried to switch tabs some of my other apps crashed saying my laptop was out of memory (I usually run around 12GB usage out of 16GB).
I checked task manager and the Serverless app had bloated to almost 4GB of ram without even being open or used. I killed the process and my machine returned to normal.
The text was updated successfully, but these errors were encountered:
I was able to reproduce the issue, and the fix for not properly closing the app has been released as part of 0.0.160. I'll continue to investigate why memory usage may have crept up.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I installed the beta last week and I've been installing each update as they come so I'm up to date.
I logged in with my account and have switched organizations, but due to another bug #20 I haven't used the new app much.
I closed out of the app, but apparently the process was still running in the background, and almost 24 hours later my operating system started grinding to a halt, and when I tried to switch tabs some of my other apps crashed saying my laptop was out of memory (I usually run around 12GB usage out of 16GB).
I checked task manager and the Serverless app had bloated to almost 4GB of ram without even being open or used. I killed the process and my machine returned to normal.
The text was updated successfully, but these errors were encountered: