Re: New packet list - out of memory?

[didier <dgautheron () magic fr>]

Le mardi 06 octobre 2009 à 15:30 -0400, Jeff Morriss a écrit :

> Trying that on Linux (64-bit) with a capture file of mine, I get (all 
> with SVN 30347, new packet list):
>
> (no env settings)
> CPU time ("user time" from 'times'): 40.491 seconds
> VSZ (from ps aux): 995,644
>
> With WIRESHARK_DEBUG_SE_NO_CHUNKS set:
> CPU time: 43.048 seconds
> VSZ: 1,128,076
>
> With WIRESHARK_DEBUG_EP_NO_CHUNKS and WIRESHARK_DEBUG_SE_NO_CHUNKS set:
> CPU time: 48.536 seconds
> VSZ: 1,120,308
>
>
> (It's a bit odd that memory usage goes up when chunks are off.)
In this case wireshark allocates a emem_chunk_t (28 bytes on a 32bits
system) for each ep/se_alloc call.
 
> Maybe Windows doesn't like big (10Mb) allocations?  Another thing is
Maybe an option would be to replace it with g_malloc.

Didier


___________________________________________________________________________
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