beepcore-c memory purity?

I was wondering how well-tested memory allocation/deallocation is in 
beepcore-c.  I find that pushing a few hundred messages (totaling a 
few hundred MB) through a frame-oriented BEEP application, memory usage 
creeps up rather alarmingly.  I'm not quite sure yet if the memory usage 
is per-frame or per-message just yet, but it increases a lot more on a 
large message than a small one.

It is of course possible that it is in my application, but I don't see any 
OBVIOUS leaks there.  If anyone can vouch for beepcore-c having been 
tested for memory leaks, that would help narrow my search a great deal.  I 
am pretty confident bpc_frame_destroy() is reliably called on each frame, 
for example.

I'm getting ready to release this application as open source in the fairly 
near future, but I definitely need to track this one down first.

-------------------------------------------------------
-- David C. Niemi           Adeptech Systems, Inc.   --
-- Reston, Virginia, USA    http://www.adeptech.com/ --
-------------------------------------------------------



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click