Use a GMemChunk for allocating and freeing "frame_data" structures; it
authorguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Mon, 3 Apr 2000 08:42:45 +0000 (08:42 +0000)
committerguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Mon, 3 Apr 2000 08:42:45 +0000 (08:42 +0000)
commit4fab52549246a6decde241fa65f2c8b0041a4e98
treeed934975fa564e2ed1bc4ec60be32d4dde1dd242
parenta7f8fde347a233a0964b079d408275baa2739fed
Use a GMemChunk for allocating and freeing "frame_data" structures; it
reduces the memory required for one big capture file I have by about 10
megabytes, and speeds up the reading in of that file, presumably because
it amortizes the memory-allocator space and CPU time overhead over
a set of several "frame_data" structures.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@1776 f5534014-38df-0310-8fa8-9805f1628bb7
file.c
file.h