not a solution - but a work around perhaps you could get wireshark to use multiple files so that you don't end up with one giant capture file
/d On 09/05/07, d a <[EMAIL PROTECTED]> wrote:
Twice now I ran wireshark (in non promiscuous mode) for approx 1 1/2 hours. When I tick "stop" the data compiles until about 15% and then I get an error window that reads "Out of Memory" Wireshark must close " (or something like that). I lose the entire capture. Im running WinXP SP2 with 1 gig ofRAM. Is the problem due to low RAM or is it something else? How can I avoid this in the future? How does wireshark make use of memory while its running? Thanks Dave ------------------------------ Ahhh...imagining that irresistible "new car" smell? Check out new cars at Yahoo! Autos.<http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-> _______________________________________________ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
-- The famous philosopher Rene Descartes walked into a bar. "Can I get you a drink?", the barman asked. "I think not," Descartes replied... and instantly disappeared in a puff of smoke.
_______________________________________________ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
