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

            Bug ID: 14489
           Summary: tshark memory leaks with asan / valgrind [file not
                    found] (10/10)
           Product: Wireshark
           Version: Git
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: Major
          Priority: Low
         Component: Common utilities (libwsutil)
          Assignee: bugzilla-ad...@wireshark.org
          Reporter: otto.air...@gmail.com
  Target Milestone: ---

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 file_not_found

==52169== HEAP SUMMARY:
==52169==     in use at exit: 96,838 bytes in 73 blocks
==52169==   total heap usage: 50,857 allocs, 50,784 frees, 25,949,059 bytes
allocated
==52169==
==52169== Thread 1:
==52169== 15 bytes in 1 blocks are definitely lost in loss record 17 of 67
==52169==    at 0x4C2DB8F: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==52169==    by 0xA952718: g_malloc (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==52169==    by 0xA96B4EE: g_strdup (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==52169==    by 0x40DB86: main (tshark.c:1272)
==52169==
==52169== 22 bytes in 1 blocks are definitely lost in loss record 20 of 67
==52169==    at 0x4C2DB8F: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==52169==    by 0xB6AEA17: __vasprintf_chk (vasprintf_chk.c:80)
==52169==    by 0xA990C98: g_vasprintf (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==52169==    by 0xA96B66C: g_strdup_vprintf (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==52169==    by 0xA96B728: g_strdup_printf (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2)
==52169==    by 0x42A36A: cfile_open_failure_message (failure_message.c:66)
==52169==    by 0x41860B: cf_open (tshark.c:4073)
==52169==    by 0x40EEC9: main (tshark.c:2009)
==52169==
==52169== LEAK SUMMARY:
==52169==    definitely lost: 37 bytes in 2 blocks
==52169==    indirectly lost: 0 bytes in 0 blocks
==52169==      possibly lost: 0 bytes in 0 blocks
==52169==    still reachable: 96,801 bytes in 71 blocks
==52169==         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