Re: [Bug 7775] Wireshark leaks memory when selecting packets

[Jakub Zawadzki <darkjames-ws () darkjames pl>]

On Mon, Oct 08, 2012 at 06:29:33PM -0400, Evan Huus wrote:
> It doesn't crash, yes, but it leaks again. I've added
> emem_destroy_chunk() for now in revision 45412, 

I forgot to note that emem_destroy_chunk() works only with chunks
created with emem_create_chunk()

emem_create_chunk_gp() changes npc->buf, and amount_free_init
So it leaks 2 * page_size (8KiB) per packet ;|

Still I don't understand why it fails assertion when doing mprotect()
[bug #7814].

> until I can spend some time figuring out the correct logic for sharing freed blocks.

I tried different approach, use one pool for ep_ memory, but each chunk can have different ->id,
attaching proof.

Heh, I start to think that we should just use Boehm GC...

Attachment: a.patch
Description:

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe