-
-
Notifications
You must be signed in to change notification settings - Fork 203
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
Leak in VACM context table #149
Comments
Hey, thanks for your nitpicking! ;-) Do you actually notice this leak? It leaks noticeably when you register a whole lot of different context names. The problem here is that But my question is if there is actually a use-case where it makes a difference? |
Hi Ilya, I actually got in to trouble with this leak. I recently sent you an email with my application description on March 28th. Maybe you remember the SNMP agent proxy ... The proxy is an accessor for IoT nodes in a meshed network topology. The nodes appear dynamically using some kind of IPv6 neighbor discovery. Each node has an UID, which is used also as SNMP context identifier. If now a branch of the network is removed, the VACM and related entries are remaining in the MIB tree... |
Thanks, this helps to get rid of outdated context table entries. The next potentially leaky code section might be in |
Hi Ilya,
are there any considerations from your side to fix the following leak?
pysnmp/pysnmp/entity/config.py
Line 451 in 0ab27d2
Regards,
Andreas
The text was updated successfully, but these errors were encountered: