Comment # 8
on bug 8281
from David Eichar
(In reply to comment #7)
> (In reply to comment #6)
> > I'm sufficiently convinced at this point that this isn't a Wireshark bug in
> > particular, just a GTK issue.
> >
> > I'm afraid their isn't much we can do about it. One workaround you could use
> > would be to install a nightly trunk build from
> > https://www.wireshark.org/download/automated/. There should be an option in
> > the installer for an experimental interface that uses Qt instead of GTK -
> > presumably it won't suffer from this bug, though it is still fairly basic at
> > this point.
>
> Another option is to build with GTK3 and see if the bug is fixed there.
> We could let the buildbot do a couple of GTK3 builds for test purposes.
I download Wireshark-win32-1.9.0-SVN-47676 onto a Windows Server 2008 32-bit
system and tested Qtshark while logged in via Remote Desktop. I am happy to
report that Qtshark does not have the problem with memory usage, while
Wireshark still does. If someone builds a version of Wireshark with GTK3, let
me know and I will be happy to test it for the excess memory usage.
You are receiving this mail because:
- You are watching all bug changes.
