Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 5892] Wireshark capture cannot be stopped under heavy traffic rate

[bugzilla-daemon@xxxxxxxxxxxxx]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5892

Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #6336|review_for_checkin?         |review_for_checkin-
              Flags|                            |

--- Comment #11 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2012-06-14 06:20:24 PDT ---
Comment on attachment 6336
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6336
proposed change for stop button issue - note the patch is for version 1.2.6 and
for non-windows env

I think a better way to approach this would be to indicate to the user what's
going on: some kind of status indication or maybe even a progress bar could pop
up to indicate that we're catching up with the captured packets (i.e., we're
dissecting stuff that has already been captured).

Preventing dissection of the packets that have already been captured (but are
in the file) doesn't seem very good--and may have weird/unexpected results if,
for example, the user then wants to save the temporary file: do they get all
the dissected frames or all the frames in the temporary file?

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.