Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 2375] Wireshark memory leak with each file open and/or display filter change

[bugzilla-daemon@xxxxxxxxxxxxx]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2375


Bill Meier <wmeier@xxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




--- Comment #5 from Bill Meier <wmeier@xxxxxxxxxxx>  2009-10-16 12:32:30 PDT ---
I'm marking this as closed since all the cases related to the use of GMemChunks
by specific dissectors have now been fixed.

Note that the use of GMemChunks in the NCP dissector was the probable cause of
the problem reported by the OP.

I expect these fixes will be available in the next maintenance release (1.2.3).

There are, however, undoubtedly other memory leaks. Bugs can be filed when it
is possible to provide a test case showing a significant leak.

For example: see https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4134\


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