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

            Bug ID: 14484
           Summary: tshark memory leaks with asan / valgrind [Inter-ORB]
                    (5/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 16198
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16198&action=edit
recording 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>

==49641== HEAP SUMMARY:
==49641==     in use at exit: 96,839 bytes in 72 blocks
==49641==   total heap usage: 53,604 allocs, 53,532 frees, 49,833,254 bytes
allocated
==49641==
==49641== Thread 1:
==49641== 43 bytes in 1 blocks are definitely lost in loss record 43 of 66
==49641==    at 0x4C2DB8F: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==49641==    by 0xA952718: g_malloc (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==49641==    by 0xA96B567: g_strndup (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==49641==    by 0x6DE44C6: get_modname_from_repoid (packet-giop.c:1700)
==49641==    by 0x6DE44C6: try_explicit_giop_dissector (packet-giop.c:1993)
==49641==    by 0x6DE7459: dissect_giop_request_1_2 (packet-giop.c:4526)
==49641==    by 0x6DE7459: dissect_giop_common (packet-giop.c:4851)
==49641==    by 0x7336575: tcp_dissect_pdus (packet-tcp.c:3612)
==49641==    by 0x6DE4882: dissect_giop_tcp (packet-giop.c:4944)
==49641==    by 0x6DE81B4: dissect_giop_heur (packet-giop.c:4987)
==49641==    by 0x6A9E761: dissector_try_heuristic (packet.c:2701)
==49641==    by 0x7336B35: decode_tcp_ports (packet-tcp.c:5556)
==49641==    by 0x7336D74: process_tcp_payload (packet-tcp.c:5611)
==49641==    by 0x733748F: desegment_tcp (packet-tcp.c:3134)
==49641==    by 0x733748F: dissect_tcp_payload (packet-tcp.c:5684)
==49641==
==49641== 43 bytes in 1 blocks are definitely lost in loss record 44 of 66
==49641==    at 0x4C2DB8F: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==49641==    by 0xA952718: g_malloc (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==49641==    by 0xA96B567: g_strndup (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==49641==    by 0x6DE44C6: get_modname_from_repoid (packet-giop.c:1700)
==49641==    by 0x6DE44C6: try_explicit_giop_dissector (packet-giop.c:1993)
==49641==    by 0x6DE7459: dissect_giop_request_1_2 (packet-giop.c:4526)
==49641==    by 0x6DE7459: dissect_giop_common (packet-giop.c:4851)
==49641==    by 0x7336575: tcp_dissect_pdus (packet-tcp.c:3612)
==49641==    by 0x6DE4882: dissect_giop_tcp (packet-giop.c:4944)
==49641==    by 0x6A9C06A: call_dissector_through_handle (packet.c:694)
==49641==    by 0x6A9D091: call_dissector_work (packet.c:779)
==49641==    by 0x6A8D5D9: try_conversation_call_dissector_helper.isra.7
(conversation.c:1245)
==49641==    by 0x6A8E5D0: try_conversation_dissector (conversation.c:1275)
==49641==    by 0x733669B: decode_tcp_ports (packet-tcp.c:5493)
==49641==
==49641== LEAK SUMMARY:
==49641==    definitely lost: 86 bytes in 2 blocks
==49641==    indirectly lost: 0 bytes in 0 blocks
==49641==      possibly lost: 0 bytes in 0 blocks
==49641==    still reachable: 96,753 bytes in 70 blocks
==49641==         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