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 Oct 24, 2020. It is now read-only.
We are using this library in opsdroid and have noticed that when leaving the RTM websocket connected for a period of time (24-48 hours) memory will suddenly increase rapidly. We are tracking the issue in opsdroid/opsdroid#743 but I wanted to also raise it here to aid with debugging.
My initial guess would be that the Slack end of the connection is closing or restarting the websocket and there is a bug either here or in the upstream slacker library which is getting stuck and using more memory until it gets OOM killed.
Any assistance with troubleshooting this woudl be much appreciated.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We are using this library in opsdroid and have noticed that when leaving the RTM websocket connected for a period of time (24-48 hours) memory will suddenly increase rapidly. We are tracking the issue in opsdroid/opsdroid#743 but I wanted to also raise it here to aid with debugging.
My initial guess would be that the Slack end of the connection is closing or restarting the websocket and there is a bug either here or in the upstream slacker library which is getting stuck and using more memory until it gets OOM killed.
Any assistance with troubleshooting this woudl be much appreciated.
The text was updated successfully, but these errors were encountered: