Wireshark-bugs: [Wireshark-bugs] [Bug 9243] Buildbot crash output: fuzz-2013-10-07-8828.pcap

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 07 Oct 2013 17:13:19 +0000

changed bug 9243

What Removed Added
CC   [email protected]

Comment # 1 on bug 9243 from 
I'm also seeing the following memory leaks with this capture:

==20971== 156,265 (168 direct, 156,097 indirect) bytes in 3 blocks are
definitely lost in loss record 21,110 of 21,115
==20971==    at 0x4C2A2DB: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==20971==    by 0x94F1DC0: g_malloc (gmem.c:104)
==20971==    by 0x950795D: g_slice_alloc (gslice.c:1016)
==20971==    by 0x9507E9D: g_slice_alloc0 (gslice.c:1042)
==20971==    by 0x64A9EF9: fragment_add_seq_common (reassemble.c:360)
==20971==    by 0x64AA157: fragment_add_seq_check_work (reassemble.c:1983)
==20971==    by 0x64AB157: fragment_add_seq_check (reassemble.c:2027)
==20971==    by 0x677F57C: dissect_cbch (packet-gsm_cbch.c:382)
==20971==    by 0x648D1D3: call_dissector_through_handle (packet.c:492)
==20971==    by 0x648D88F: call_dissector_work (packet.c:586)
==20971==    by 0x648F411: call_dissector_with_data (packet.c:2105)
==20971==    by 0x648D1D3: call_dissector_through_handle (packet.c:492)
==20971== 
==20971== 168,352 (168 direct, 168,184 indirect) bytes in 3 blocks are
definitely lost in loss record 21,111 of 21,115
==20971==    at 0x4C2A2DB: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==20971==    by 0x94F1DC0: g_malloc (gmem.c:104)
==20971==    by 0x950795D: g_slice_alloc (gslice.c:1016)
==20971==    by 0x9507E9D: g_slice_alloc0 (gslice.c:1042)
==20971==    by 0x64A9EF9: fragment_add_seq_common (reassemble.c:360)
==20971==    by 0x64AA157: fragment_add_seq_check_work (reassemble.c:1983)
==20971==    by 0x64AB157: fragment_add_seq_check (reassemble.c:2027)
==20971==    by 0x677F0F6: dissect_cbch (packet-gsm_cbch.c:394)
==20971==    by 0x648D1D3: call_dissector_through_handle (packet.c:492)
==20971==    by 0x648D88F: call_dissector_work (packet.c:586)
==20971==    by 0x648F411: call_dissector_with_data (packet.c:2105)
==20971==    by 0x648D1D3: call_dissector_through_handle (packet.c:492)

You are receiving this mail because:
  • You are watching all bug changes.