Wireshark-bugs: [Wireshark-bugs] [Bug 4115] Wireshark crashes while opening large trace files on
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4115
--- Comment #6 from Ian Schorr <ian.schorr@xxxxxxxxx> 2009-10-12 19:09:12 PDT ---
Actually, while 1.3.0 still has this problem for me, so far I haven't been able
to produce the crashes using the auto-built SVN 30553 release.
Well, it did crash once, this time with a somewhat different error:
10/13/09 12:53:25 PM wireshark-bin[2346] wireshark-bin(2346,0xa0234500)
malloc: *** mmap(size=16777216) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
10/13/09 12:53:25 PM [0x0-0x19b19b].org.wireshark.Wireshark[2341]
wireshark-bin(2346,0xa0234500) malloc: *** mmap(size=16777216) failed (error
code=12)
10/13/09 12:53:25 PM [0x0-0x19b19b].org.wireshark.Wireshark[2341] ***
error: can't allocate region
10/13/09 12:53:25 PM [0x0-0x19b19b].org.wireshark.Wireshark[2341] *** set
a breakpoint in malloc_error_break to debug
10/13/09 12:53:25 PM [0x0-0x19b19b].org.wireshark.Wireshark[2341]
GLib-ERROR **: gmem.c:136: failed to allocate 16520 bytes
10/13/09 12:53:25 PM [0x0-0x19b19b].org.wireshark.Wireshark[2341]
aborting...
...Though I haven't been able to reproduce this again with any of my captures
(including the one it originally crashed on), whereas before it crashed
consistently at the exact same point in a variety of traces (though different
point in each trace).
I don't think it's simply the lower memory requirements of the new list widget,
though seems possible that it's related. In 1.2.2 I have traces that crash
after loading 55,000 packets and allocating about 100MB. In 30553 it doesn't
crash after loading about 480,000 packets and allocating about 400MB.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
