Ethereal-dev: Re: [Ethereal-dev] Ethereal-win32 : Memory not de-allocated when closing an old

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Guy Harris <gharris@xxxxxxxxx>
Date: Mon, 07 Mar 2005 13:27:39 -0800
Alex Lam wrote:
I believe there is a memory leak in Ethereal-win32, v0.10.9, but dated back to at least 0.10.7. The symptom is that memory is not de-allocated when you close a previous capture with the File->close menu command. 

What if you then open a new file?
We don't have separate "initialize" and "clear" routines for dissectors, with the latter one freeing up data structures maintained by the dissector for a capture, and the former one initializing those data structures; we just have an "initialize" routine which does both. 


In fact, each time you change the display filter, more memory is
required, even when you are just toggling between 2 filters.


So you've found a leak even when you *don't* close captures?