https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15087
--- Comment #4 from Dylan <daul...@gmail.com> ---
"In your original case, do you really want to stop right at the point where the
filter is hit? Or would you like to continue capturing a few more packets for
context?"
In https://code.wireshark.org/review/#/c/29195, Christopher Maynard mentioned
it would be nice to have a configurable delay after the trigger condition.
I don't think it will ever be exact because the display filter processing is
done separately than capturing. The current implementation in that review lags
up to 1 second in my testing. But, I'm OK with it stopping at some point after
the capture. It doesn't have to be exact for my needs.
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
