Wireshark-bugs: [Wireshark-bugs] [Bug 13184] Access violation in Wireshark!rescan_packets+0x345

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 29 Nov 2016 21:03:47 +0000

changed bug 13184


What Removed Added
Status UNCONFIRMED CONFIRMED
Ever confirmed   1

Comment # 6 on bug 13184 from 
The minidump seems sufficient.
We are still looping in the rescan_packet() function while the file has been
closed (cf->state == FILE_CLOSED).
Did you apply several filters and close Wireshark (or the capture file) soon
after? I was not able to reproduce the exact same crash on my Linux box today
but another similar one.
We should probably either break the loop if the file is closed during its
processing, or abort it somehow when closing the file (if this is really
asynchronous, I do not know well this code part).

You are receiving this mail because:
  • You are watching all bug changes.