[Quickfix-users] Memory Leak
Brought to you by:
orenmnero
From: Monheit, D. <Dav...@ci...> - 2006-09-29 11:44:10
|
Well. After spending some more time with Purify and valgrind, I am starting to think that there is not an actual leak, but more of a "hoarding" of memory !!! There is no question that the program grows and grows (as per the previous posting) but now I am not convinced that it is because of a leak. Oren, what do you reckon is the normal memory foot print of a simple quickfix app which just return from fromApp without doing anything? Why when I just instantiate a message from a string, over and over again, the footprint is stable. When I start using the copy constructor the foot print grows even though the program is not really doing anything? What is it about repeating groups that could induce this observations? Both valgrind and purify don't detect any significant leak (when compared to the footprint) when one calls initiator.stop() and then exit(). I am puzzled and frustrated :-) Regards David ------------------------------------------------------- David Monheit Citadel Investment Group (Europe) Ltd Tel +44 (0) 20 7645 9715 Mob +44 (0) 7968 988 218 ------------------------------------------------------------------------ ------------------------------------------------------------------------ -- The contents of this message and any attachments may be privileged, confidential and proprietary. If you are not an intended recipient, please inform the sender of the transmission error and delete this message immediately without reading, disseminating, distributing or copying the contents. Citadel makes no assurances that this e-mail and any attachments are free of viruses and other harmful code. Citadel Investment Group (Europe) Ltd is authorized and regulated by the Financial Services Authority (FSA Firm Ref No 190260). Registered in England and Wales. Registration No. 3666898. Registered Office: 10th Floor, 2 George Yard, Lombard Street, London EC3V 9DH. |