Ethereal-users: [Ethereal-users] Follow TCP Stream, display Hex hangs or takes excessive cpu

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: David Moore <davem@xxxxxxxxx>
Date: Tue, 25 Jan 2005 14:48:17 -0500
I posted this a while back but never saw any kind of resolution. I just tried the latest 10.9 release and it's still a problem. 

This problem seems to have been introduced somewhere around ethereal 9.4

----------------------------
* Subject: [Ethereal-users] Follow TCP Stream, display Hex hangs for large stream 
* From: David Moore <davem@xxxxxxxxx>
* Date: Wed, 22 Sep 2004 10:35:58 -0400
I've noticed a problem in at least the last two releases 10.5 & 10.6 of Ethereal that did not occur in earlier circa 9.1? versions.
Do a "Follow TCP Stream", after the default display in ASCII comes up I then select any other format, (typically Hex). If the stream is relatively large, the redisplay in the nex format takes unusually long to forever.
In my largest case, I have 10 meg stream. "Follow TCP Stream" takes approximately 90 seconds to produce the ASCII stream. Selecting "Hex" results in the CPU pegging at 100% and even after 2 hours never produced a display.
This same data set did not have this problem with versions of ethereal from about a year ago. 

 My main machine is runnning RedHat 9.0, 3.0 GHz, with 1 GB of ram.
I'have identical results on a laptop with Fedora Core 2, 1.6 GHz, 1 GB ram. 

----------------------------