https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14487

            Bug ID: 14487
           Summary: tshark memory leaks with asan / valgrind [sip + rtp]
                    (8/10)
           Product: Wireshark
           Version: Git
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: Major
          Priority: Low
         Component: Dissection engine (libwireshark)
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: otto.air...@gmail.com
  Target Milestone: ---

Created attachment 16203
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16203&action=edit
file causing tshark to leak memory

Build Information:
TShark (Wireshark) 2.5.1 (v2.5.1rc0-467-g2eb6f3b5)
Built using clang 4.2.1 Compatible Clang 3.8.0 (tags/RELEASE_380/final).
--
tshark leaking memory when executing command:

valgrind tshark -2 -V -r <filename>

==49667==     in use at exit: 96,757 bytes in 71 blocks
==49667==   total heap usage: 53,937 allocs, 53,866 frees, 52,111,584 bytes
allocated
==49667==
==49667== Thread 1:
==49667== 4 bytes in 1 blocks are definitely lost in loss record 7 of 65
==49667==    at 0x4C2DB8F: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==49667==    by 0xA952718: g_malloc (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==49667==    by 0x77B9173: wmem_memdup (wmem_miscutl.c:23)
==49667==    by 0x6E7FA70: alloc_address_wmem (address.h:147)
==49667==    by 0x6E7FA70: copy_address_wmem (address.h:265)
==49667==    by 0x6E7FA70: copy_address (address.h:275)
==49667==    by 0x6E7FA70: find_or_create_call_info_conv (packet-h223.c:530)
==49667==    by 0x6E7FA70: find_or_create_call_info (packet-h223.c:551)
==49667==    by 0x6E7FA70: dissect_h223_common (packet-h223.c:1279)
==49667==    by 0x6E7FC6D: dissect_h223_bitswapped (packet-h223.c:1387)
==49667==    by 0x6A9C06A: call_dissector_through_handle (packet.c:694)
==49667==    by 0x6A9D091: call_dissector_work (packet.c:779)
==49667==    by 0x6A9DCBC: dissector_try_string_new (packet.c:1660)
==49667==    by 0x6A9DD10: dissector_try_string (packet.c:1685)
==49667==    by 0x721CC2B: process_rtp_payload (packet-rtp.c:1540)
==49667==    by 0x721CE4B: dissect_rtp_data (packet-rtp.c:1685)
==49667==    by 0x721EC30: dissect_rtp (packet-rtp.c:2473)
==49667==
==49667== LEAK SUMMARY:
==49667==    definitely lost: 4 bytes in 1 blocks
==49667==    indirectly lost: 0 bytes in 0 blocks
==49667==      possibly lost: 0 bytes in 0 blocks
==49667==    still reachable: 96,753 bytes in 70 blocks
==49667==         suppressed: 0 bytes in 0 blocks

Credit goes to: Otto Airamo and Antti Levomäki, Forcepoint

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to