Wireshark-bugs: [Wireshark-bugs] [Bug 7833] Visual C++ Runtime Library "...the application has r
Comment # 19
on bug 7833
from Guy Harris
(In reply to comment #18)
> I quickly discovered
> that it isn't necessary to have *any* captured data displayed at all to
> invoke this bug. Simply run Wireshark, grab one side of the window, and
> wiggle it around
That's with Wireshark showing the welcome screen, with the interface list, list
of recently opened files, etc., rather than showing the packet list/packet
details/hex dump pane, or is it just showing empty packet list/packet
details/hex dump panes?
> while watching the Mem_Useage and VM_Size columns of the
> wireshark.exe process entry in Task Manager. Within a few seconds it will
> grow from the initial 70-80MB through hundreds of MB, and in another few
> seconds it will exceed 1.8 - 2 GB and crash. This is 100% repeatable. It is
> not necessary to touch any button, control, menu item, or anything. Simply
> grab the window edge and start waving it around. Note that grabbing the
> title bar at the top of the window and moving the whole window around on the
> screen will also cause the memory useage to grow considerably, but at a much
> slower rate than when doing the re-sizing action.
Please file that as a separate bug; it *might* be the same as this bug, but it
might not be. Your bug is clearly *not* a bug in the dissecting code, as there
aren't any captured packets; it's probably either a bug in the Windows version
of GTK+ or in whatever Wireshark code gets invoked on resizes and moves (it
saves size and possibly position information to a file, but I have difficulty
seeing that chew up memory that fast; we have some of our own widgets that
might be handling those events, but I'm not sure any of them would be active if
you're on the welcome screen.
I wasn't able to reproduce it with the same Wireshark version on my 32-bit XP
SP3 virtual machine; perhaps it's some issue with the graphics adapter driver
or an issue with GTK+ that only shows up with some graphics adapters?
You are receiving this mail because:
- You are watching all bug changes.
