Ask Your Question
0

Slow capture restart

asked 2017-11-10 19:48:14 +0000

PavelP gravatar image

Any idea why restarting capture is extremely slow in wireshark (if the amount of captured data was large)? I use Version 2.4.2 (v2.4.2-0-gb6c63ae086) and I capture around 100MB of udp packets, when i try to restart capture it takes extremely long time (over 10 seconds) and wireshark blocks entire window and becomes unresponsive during this time.

I have enough ram, it shouldn't block on that, should just close that existing capture run (by releasing all associated resources) in some background thread.

Another point: I prefer to use keyboard shortcuts to restart capture and "Continue without Saving". The Ctrl+R dialog (to restart capture) doesn't handle properly keyboard input, if I press Tab or [right/left] the "Continue without Saving" button doesn't get the same handling as the other two.

edit retag flag offensive close merge delete

Comments

As for the last part, please file a bug report.

Jaap gravatar imageJaap ( 2017-11-11 00:22:25 +0000 )edit

Note that 2.4.2 is long out of support, so if there are any changes to be made, at best they'll appear in 3.2 and 3.4. If this is a distribution built version (Redhat, etc.) then they might backport the change, but that's entirely up to them.

grahamb gravatar imagegrahamb ( 2020-11-25 08:54:36 +0000 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2020-11-25 08:46:30 +0000

hugo.vanderkooij gravatar image

Even with anough RAM it takes some time to clear out the old data and prepare for a new capture.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2017-11-10 19:48:14 +0000

Seen: 156 times

Last updated: Nov 25