Bug #10624
closed
Memory leak in Unbound with Python module and DHCP lease registration active
Added by Adrien Carlyle over 4 years ago.
Updated over 1 year ago.
Plus Target Version:
23.01
Affected Architecture:
All
- Subject changed from Unbound configuration memory leak to Unbound configuration memory leak with python module + register DHCP leases active
This would likely be fixed by also solving #5413 since it wouldn't restart in this case. Though the actual memory leak should be re-tested on unbound 1.13.1 and if it's still present, it should be reported upstream to the Unbound devs.
- Related to Bug #5413: Incorrect Handling of Unbound Resolver [service restarts, cache loss, DNS service interruption] added
- Assignee set to Christian McDonald
- Status changed from New to Confirmed
This is confirmed.
Python3.9 and lower has some deeply rooted memory management problems. Because of the way Unbound reinitializes the Python context every time Unbound is reloaded via unbound-control reload or kill -HUP, some memory is leaked.
Moving to Python3.10+ greatly improves this situation.
- Target version set to 2.7.0
- Plus Target Version set to 23.01
- Release Notes set to Default
- Affected Architecture All added
- Affected Architecture deleted (
SG-1100, SG-3100)
- Status changed from Confirmed to Feedback
- Subject changed from Unbound configuration memory leak with python module + register DHCP leases active to Memory leak in Unbound with Python module and DHCP lease registration active
- Start date deleted (
06/02/2020)
Updating subject for release notes.
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
No reports of problems that I've seen since the fix is in place. If it recurs we can always reopen or start a fresh issue as needed.
Also available in: Atom
PDF
Updated by 
Updated by