Wireshark-bugs: [Wireshark-bugs] [Bug 5219] New: LUA Memory Leak

Date: Wed, 15 Sep 2010 11:09:40 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5219

           Summary: LUA Memory Leak
           Product: Wireshark
           Version: 1.4.0
          Platform: x86-64
        OS/Version: Windows 7
            Status: NEW
          Severity: Normal
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: laabs@xxxxxx


Build Information:
Version 1.4.0 (SVN Rev 34005 from /trunk-1.4)

Copyright 1998-2010 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GTK+ 2.16.6, (64-bit) with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, without
SMI, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.8.5, with
Gcrypt 1.4.5, without Kerberos, with GeoIP, with PortAudio V19-devel (built Aug
29 2010), with AirPcap.

Running on 64-bit Windows 7, build 7600, with WinPcap version 4.1.2 (packet.dll
version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729
--
When using a LUA Dissector Wireshark leaks memory for each packet and each call
to tvb:range([offset], [length]) independent of offset and length.
Calling the garbage collection from within LUA does not help.
The same amount of memory is leaked every time a new display filter is applied.

Mimimized dissector code (leaks about 4kB per packet):

-- udt memory leak dissector
memleak = Proto("memleak", "memleak", "memleak")
function memleak.dissector(buf, pinfo, tree)
    for i = 0, 100, 1 do
        buf(0, 1)
    end
end
udp_table:add (0, memleak)

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.