This is our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

That's my biggest complain. Sometimes I fire it up to capture sip||rtp and forget about it. When I come back next day my PC feels crippled. Sometimes I don't notice that problem right away and keep working half a day on barely breathing pc.

Isn't there some kind of backup file for ongoing capture to dump excessively huge captures? Why is that wireshark.exe ends up eating 4-5GB of ram over a couple of days??

One suggestion is to save as much data to a file when wireshark is minimized (e.g. when it cannot be used by scrolling in realtime capture list etc). So that in this mode the beast doesn't kill my pc.

asked 29 Sep '13, 17:29

psp80's gravatar image

psp80
1223
accept rate: 0%


Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×23

question asked: 29 Sep '13, 17:29

question was seen: 3,229 times

last updated: 29 Sep '13, 17:37

p​o​w​e​r​e​d by O​S​Q​A