https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7771
--- Comment #3 from Jim Young <jyoung@xxxxxxx> 2012-09-30 11:22:42 PDT ---
Created attachment 9254
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=9254
Picture of Windows XP task-manager's CPU and Memory usage triggered by
TCP-Graph processing
I've recently seen similar TCP-Graph problems both on local built OSX and on
the Buildbot XP versions. But in my case the TCP-Graphs do not appear to
directly "crash" wireshark, instead they appear to consume CPU for a very very
very long time.
The attached picture is snapshot taken from Window's XP Task-manager while one
particular tracefile was processed to create a Stevens style graph. The XP
Task-manager graph shows a fascinating CPU and memory usage pattern while
Wireshark's tcp-graph processing was in progress. It took approximately 427
seconds before the TCP-Graph window finally was displayed. After waiting all
that time the final Steven's graph displayed was blank! This Steven's graph
attempt was from a relatively short/small tcp trace file that displayed just
fine within a second or two in an older Wireshark version.
I'll try to upload a sanitized version of the trace file I used when I grabbed
the XP Task Manager usage snapshot if anyone thinks that might be useful.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.