Wireshark-bugs: [Wireshark-bugs] [Bug 5184] Out of memory problem - Wireshark files capturing
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 6 Sep 2010 13:56:07 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5184

--- Comment #4 from Guy Harris <guy@xxxxxxxxxxxx> 2010-09-06 13:56:04 PDT ---
If the saved file has all the packets in it, then, if you try to open it in
Wireshark, Wireshark will run out of memory.  This problem has nothing to do
with *capturing* packets - it has to do with *dissecting* packets.  When
Wireshark captures traffic, it runs dumpcap to have it write every captured
packet to a file, and then gets messages from dumpcap saying "N more packets
have arrived".  As each such message arrives, Wireshark reads in the packets.

So, from the point of view of Wireshark, a capture is just a
packet-burst-by-packet-burst read of a file.

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