https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3942
Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeff.morriss.ws@xxxxxxxxx
--- Comment #1 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2010-03-30 16:58:36 PDT ---
Looks like Wireshark ran out of memory and aborted as a result. Were you
analyzing a large capture file? I think there have been some memory-usage
related fixes since 1.2.1 too, so you might want to try a newer stable version
or (better yet) the development version (1.3.x).
Also see:
http://wiki.wireshark.org/KnownBugs/OutOfMemory
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
