http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2407
--- Comment #3 from Jim Young <jyoung@xxxxxxx> 2008-04-03 15:31:52 GMT ---
Hello Japp,
I saw one user at sharkfest (Patrick was that you?) who had a relatively large
trace file (but I don't recall the number of packest) that contained what he
called "intersting data" that would trigger this same bug.
After he selected the "Expert Info Composite" item, the system would start the
normal processing (both the "Expert Infos" and the transient "Reprocessing: all
packets" windows would be created) but the application would soon crash which
resulted in the standard Windows application error dialog.
I first thought I had heard the sharkfest attendee say that Wireshark and/or
Windows had reported a memory problem. But when I had him replicate the
problem with the Windows task manager open and watching the "Performance" tab
we could see that his system had plenty of real memory when the system crashed.
After the crash we did NOT see any out of memory errors messages, just the
typical "Do you want to tell Microsoft about it" dialog.
I suggested that he open a bug report.
To me it really looked like this bug was trigged by something specific with
some frame (or frames) within his particular trace file.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
