Roger
changed
bug 7833
Comment # 18
on bug 7833
from Roger
Yesterday (5-Aug-2013) I installed Wireshark (Version 1.10.1 (SVN Rev 50926
from /trunk-1.10)) on my 32-bit XP SP3 system, and almost immediately ran up
against this bug. I found the description of the problem at
http://wiki.wireshark.org/KnownBugs/OutOfMemory. It certainly sounds complex,
but I also thought it ludicrous that a capture file with only 12 frames in it
(general101.pcapng) could be responsible. 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 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.
Hope this helps.
You are receiving this mail because:
- You are watching all bug changes.