Wireshark-bugs: [Wireshark-bugs] [Bug 2980] New: Crash in Reassembly

Date: Sun, 19 Oct 2008 22:59:50 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2980

           Summary: Crash in Reassembly
           Product: Wireshark
           Version: 1.0.0
          Platform: Sun
        OS/Version: Linux (other)
            Status: NEW
          Severity: Blocker
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: arun2.b@xxxxxxxxxxx


Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
Build Information:
n g_mem_chunk_free () from /usr/lib/libglib-2.0.so.0
#1  0x00e5f689 in fragment_unhash (fragment_table=0x0, key=0xad5c188) at
reassemble.c:596
#2  0x00e60829 in fragment_add_seq_check_work (tvb=0xada94d8, offset=0,
pinfo=0xc5513e8, id=63, fragment_table=0xa2c2870, reassembled_table=0xa2c2960,
frag_number=0, frag_data_len=11, 
    more_frags=0, flags=4294967295) at reassemble.c:1648
#3  0x01271b09 in dissect_internal (tvb=0xc51df68, pinfo=0xc5513e8,
tree=0xa7109d0) at packet-internal.c:1030
#4  0x00e4cc27 in call_dissector_through_handle (handle=0xa090b08,
tvb=0xc51df68, pinfo=0xc5513e8, tree=0xa7109d0) at packet.c:409
#5  0x00e4d199 in call_dissector_work (handle=0xa090b08, tvb=0xc51df68,
pinfo_arg=0xc5513e8, tree=0xa7109d0) at packet.c:498
#6  0x00e4e824 in call_dissector (handle=0xa090b08, tvb=0xc51df68,
pinfo=0xc5513e8, tree=0xa7109d0) at packet.c:1800


Hi i am encountering a crash in Reassembly. I am facing this problem only in
case of Refreshing the loaded capture file. What is the possible reason? i am
nt able to find any clue. I am using a bulky protocol uses a lot of memory. Can
memory leak be possible reasons for this?


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.