[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wireshark-bugs
Subject:    [Wireshark-bugs] [Bug 3942] WireShark Crash on OS X 10.5.8 by
From:       bugzilla-daemon () wireshark ! org
Date:       2010-03-30 23:58:44
Message-ID: 20100330235844.5EC32D6000 () mail ! wireshark ! org
[Download RAW message or body]

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

Jeff Morriss <jeff.morriss.ws@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jeff.morriss.ws@gmail.com

--- Comment #1 from Jeff Morriss <jeff.morriss.ws@gmail.com> 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.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-request@wireshark.org?subject=unsubscribe
[prev in list] [next in list] [prev in thread] [next in thread]