BIND 10 #644: [kean] Memory leaks in asiolink

[BIND 10 Development]

#644: [kean] Memory leaks in asiolink
-------------------------------------+-------------------------------------
            Reporter:  vorner        |                        Owner:
                Type:  defect        |  UnAssigned
            Priority:  medium        |                       Status:
           Component:  Unclassified  |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20131015
         Sub-Project:  DNS           |                   Resolution:
Estimated Difficulty:  0.0           |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by kean):

 * owner:  kean => UnAssigned
 * status:  accepted => reviewing


Comment:

 This bug, which was filed over three years ago, seems to be no longer
 applicable:

 {{{
 $ valgrind --leak-check=full --show-reachable=yes $PWD/run_unittests > foo
 ==20857== Memcheck, a memory error detector
 ==20857== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
 ==20857== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright
 info
 ==20857== Command:
 /home/kean/isc/X/src/lib/asiolink/tests/.libs/run_unittests
 ==20857==
 ==20857==
 ==20857== HEAP SUMMARY:
 ==20857==     in use at exit: 4 bytes in 1 blocks
 ==20857==   total heap usage: 2,820 allocs, 2,819 frees, 366,365 bytes
 allocated
 ==20857==
 ==20857== 4 bytes in 1 blocks are still reachable in loss record 1 of 1
 ==20857==    at 0x4A068F3: operator new(unsigned long) (in
 /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
 ==20857==    by 0x52C7BDE: ??? (in /usr/lib64/liblog4cplus-1.1.so.7.0.0)
 ==20857==    by 0x52B096F: ??? (in /usr/lib64/liblog4cplus-1.1.so.7.0.0)
 ==20857==    by 0x3364C0F4F2: _dl_init (in /usr/lib64/ld-2.17.so)
 ==20857==    by 0x3364C01459: ??? (in /usr/lib64/ld-2.17.so)
 ==20857==
 ==20857== LEAK SUMMARY:
 ==20857==    definitely lost: 0 bytes in 0 blocks
 ==20857==    indirectly lost: 0 bytes in 0 blocks
 ==20857==      possibly lost: 0 bytes in 0 blocks
 ==20857==    still reachable: 4 bytes in 1 blocks
 ==20857==         suppressed: 0 bytes in 0 blocks
 ==20857==
 ==20857== For counts of detected and suppressed errors, rerun with: -v
 ==20857== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
 }}}

-- 
Ticket URL: <http://bind10.isc.org/ticket/644#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development