https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5130
--- Comment #3 from Bill Meier <wmeier@xxxxxxxxxxx> 2010-08-26 11:10:38 EDT ---
OK: I've been able to duplicate the crash.
It turns out the the occurrence of the crash (on my Fedora system at least)
depends upon the height of the "summary" pane and upon the amount of scrolling
done in the pane.
If the height of the summary window is small (say 3 lines) then the crash
doesn't happen after scrolling to frame 21, applying & clearing a filter.
If the height is (say) 10 lines:
If I scroll down so frame 21 is at the end of the summary window and then
apply/clear a filter, the crash occurs.
If I scroll down so frame 21 is at the top of the summary window and then
apply/clear a filter the crash does *not* happen.
In each test case above I restarted Wireshark.
My guess: This would seem to be somehow related to the "new packet list" logic
which (after the first full dissect pass) tries to actually dissect/display
only frames which are visible in the summary window.
Now: all I have to do is actually find the bug... :(
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.