-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
matter: Old sessions not cleaned up #19069
Comments
I will check this. It is unexpected, there is normally a limit of 5 persistent sessions per fabric. All non-persistent sessions are short-lived. |
Please use latest from development branch (after #19073) where saving of sessions is logged. I tried to reproduce with my nest-mini and rebooting the hub, but the session number still maxes at 5 per fabric. |
It looks like there are only 5 sessions per fabric being persisted (there are 5 in _matter_fabrics.json). I extracted the relevant logging to a berry function and ran it directly so that the in-memory sessions are preserved for further debugging:
|
It looks like the list that's growing unbounded is
|
Hmm. So it means that some sessions are marked as persisted but not associated to any fabric |
Should sessions that are evicted from a fabric be marked as non-persistent? A quick search shows that |
Yes you nailed it. The session is removed from the fabric but not from the session store. They are hence not removed from memory. Will fix now. |
Should be fixed now. Thanks for reporting. |
PROBLEM DESCRIPTION
Google Home seems to create a new session every day (in my case, 2 devices are creating sessions), and old sessions are never cleaned up. After a while, the device runs out of memory and restarts.
From the berry console:
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Status 0
:TO REPRODUCE
EXPECTED BEHAVIOUR
Older matter sessions should probably be cleaned up so that the device doesn't run out of memory.
The text was updated successfully, but these errors were encountered: