https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7610
Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeff.morriss.ws@xxxxxxxxx
--- Comment #2 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2012-08-09 06:59:29 PDT ---
(In reply to comment #0)
> There is a crash dump, which I have saved, but it's nearly 2 GB before
> compression, so I don't know how to get it to you.
"crash dump" as in core file (or whatever they call them on Windows) or capture
file?
If it's a capture file, try splitting it into (many) smaller pieces and find
the piece that causes Wireshark to crash and attach just that.
Also keep in mind that Wireshark doesn't work well with huge capture files; a
32-bit Wireshark (as it appears you're running) will run out of memory fairly
easily (actually it seems that 64-bit Wireshark on Windows will too, see bug
5979). 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 watching all bug changes.
