https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4037
--- Comment #9 from Jim Young <jyoung@xxxxxxx> 2010-01-27 20:12:29 PST ---
On program exit with a Window XP build and the "Test patch" applied I can
consistently see the following assert:
20:29:57 Crit file packet_list_store.c: line 426: assertion
`iter->user_data' failed
Steps to the trigger the assert (assuming the preference "Open a console
window" = "Always (debugging)"):
1 Start Wireshark
2 Click on one of the previously opened files in "Open Recent:" list (this
should open the file).
3 Wait for file to load.
4 Shutdown Wireshark by entering Alt-F4 (or click on Window's upper left
"Close" [X] widget).
Interestingly if I change step 4 and shutdown Wireshark by entering CTRL-Q (or
select the "File | Quit" menu item) the assertion is not triggered.
@Anders - in response to Comment #7
I did a number of repeat tests opening two moderately large files (50MB -
180749 frames and 78MB - 75911 frames).
Without the "Test patch" applied: the 50MB file loaded between 8.9 and 9.1
seconds (with one 3.1 second outlier[*]); the 78MB file loaded between 4.9 and
5.2 seconds (with two 1.8 second outliers[*]).
With the "Test patch" applied: the 50MB file loaded between 7.8 and 7.9
seconds; the 78MB file loaded between 3.8 and 4.1 seconds.
So the "Test patch" appears to help reduce file loading speed. :)
And as a matter of comparison of these new packet list load speeds versus the
old packet list, I did the same file load tests with the newest public release
V1.2.6: the 50MB file loaded between 37.0 and 38.4 seconds; the 78MB file
loaded between 21.0 and 21.4 seconds.
[*] Outliers - With the new packet list occasionally the trace files will
unexpectedly load MUCH quicker then expected. When this happens the Status
dialog (nn% of Loading) is not displayed and there are no intermittent packet
list updates until the entire file has loaded.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
