Wireshark-dev: Re: [Wireshark-dev] [Bug 7775] Wireshark leaks memory when selecting packets
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Bálint Réczey <balint@xxxxxxxxxxxxxxx>
Date: Fri, 26 Oct 2012 12:49:56 +0200
2012/10/10 Jakub Zawadzki <darkjames-ws@xxxxxxxxxxxx>:
> 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...
I would be really curious to see some tests about it.
Has anyone tried running Wireshark performance tests with temporary
allocations replaced with  Boehm GC allocations?

Cheers,
Balint