[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wireshark-bugs
Subject:    [Wireshark-bugs] [Bug 7771] Selecting a TCP Stream Graph causes Wireshark to crash
From:       bugzilla-daemon () wireshark ! org
Date:       2012-09-30 18:22:43
Message-ID: 20120930182243.7D93D182432 () mail ! wireshark ! org
[Download RAW message or body]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7771

--- Comment #3 from Jim Young <jyoung@gsu.edu> 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.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-request@wireshark.org?subject=unsubscribe
[prev in list] [next in list] [prev in thread] [next in thread]