jeff on 16 Jun 2009 11:05:35 -0700

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

[PLUG] Wireshark ate itself

It ate all the memory and run the cpu to 100%.  I finally managed to 
nice it, when the system complained that there was no more memory and 
closed Wireshark.

I'm guessing the capture is gone from that session, correct?

This is one of those days where in order to do something simple, thirty 
three other things have to be done first.  And so on for the next simple 


Philadelphia Linux Users Group         --
Announcements -
General Discussion  --