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
Currently, members of self.users are primarily only destroyed when Pydle or the user in question leaves a channel. However, there are numerous events that call _sync_user, which will create the user in question if they don't already exist -- including receiving a NOTICE or PRIVMSG from another user.
Since these users are not necessarily in the same channel, Pydle will never see them leaving the channel and thus never know to clean them up. This can cause the users dict to become bloated over time.
The text was updated successfully, but these errors were encountered:
I think my hackish workaround checks to see if the user I'm question shares channels with us at the end of one of the relevant methods, and -- if not -- destroys them. I'll see if I'm functional enough to dig out the source when I get home
Currently, members of
self.users
are primarily only destroyed when Pydle or the user in question leaves a channel. However, there are numerous events that call_sync_user
, which will create the user in question if they don't already exist -- including receiving a NOTICE or PRIVMSG from another user.Since these users are not necessarily in the same channel, Pydle will never see them leaving the channel and thus never know to clean them up. This can cause the users dict to become bloated over time.
The text was updated successfully, but these errors were encountered: