[Impact] At shutdown, rather than terminating normally, named aborts with an assertion failure, pointing at a memory leak. This is confusing to users, and could potentially mask an actual memory-leak that could affect runtime operation. (The actual leaked memory is a control structure that is simply not deleted due to a bad patch migration.
[test case] stop named, remove any related file in /var/crash, start it, and stop it again. no crash file should exist. If present, the trace shows main calling isc_mem_destroy (and we're dying in it's assertion that no memory has been leaked.) [regression potential] The root cause of the defect here was part of the chroot-init patch (no longer used) leaked into the random_1 patch when the patches were split up as part of going to quilt. The result was that the dst_lib_destroy() function was not called, causing the control structure for same to be "leaked" at shutdown. Other than all of the normal "a rebuild could cause anything to be broken", I don't see any issues from calling the function that upstream wants/needs t have called as we are shutting down. The worst case direct regression from from the change is that named would crash in a different way, at shutdown time. [other info] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1552801 Title: named crashed with SIGABRT in assertion_failed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1552801/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
