http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=481
ljk@xxxxxxxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ljk@xxxxxxxxxxxxxxx
Status|RESOLVED |REOPENED
Resolution|WONTFIX |
------- Comment #11 from ljk@xxxxxxxxxxxxxxx 2006-12-01 19:21 GMT -------
(In reply to comment #9)
> How about a relation to GTK2? You could try the capture stuff using tshark -V
> for full dissection. If that works normally it's not the network traffic that
> bogs the dissectors. Then you could try the GTK1 version, to see if it really
> is GTK2.
Sorry for the delay, I didn't notice your reply. Just for kicks, I ran a test
with tshark and do not see the high CPU utilization, which is what I expected.
As I mentioned in my original update, I see the spikes while just moving around
in the Wireshark menus without a capture running, or while scrolling around in
a saved log file that is already loaded. As I also mentioned, a 1 meg log can
take 3+ minutes on my machine instead of 10 seconds on a system with a similar
CPU/memory configuration.
At some point I remember trying Ethereal with GTK1 and not seeing a major
difference, if any.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
