quickfix-developers

Re: [Quickfix-developers] Memory Allocation

[Viktor P. <pohrebnyak@i.ua>]

Hi, aupadras.

What quickfix revision do you use? Do you use a MemoryStoreFactory or a
FileStoreFactory for message persistance? 

If you use a MemoryStoreFactory then the answer to your question you might
find here:  Memory Being Consumed
<http://quickfix.13857.n7.nabble.com/Memory-Being-Consumed-td6507.html>  

Regards,
Viktor



--
View this message in context: http://quickfix.13857.n7.nabble.com/Memory-Allocation-tp6541p6542.html
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.

Re: [Quickfix-developers] Memory Allocation

[Viktor P. <pohrebnyak@i.ua>]

Hi, aupadras.

So you are running a clean '1.13.3' release version from  here
<http://sourceforge.net/projects/quickfix/files/latest/download>  ? If so
then I suggest you to run a memory leak detector ( IBM Purify, Intel
Inspector XE etc ) to see what's leaking memory in your app.

We run the same clean '1.13.3' release ( Windows XP 32bit, VS2005 ) in
Production with pretty heavy incoming market data traffic ( 2000+
MarketDataIncrementalRefresh msgs/sec ) and we have no issues with memory
leaks.

Regards,
Viktor



--
View this message in context: http://quickfix.13857.n7.nabble.com/Memory-Allocation-tp6541p6544.html
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.

Re: [Quickfix-developers] Memory Allocation

[Viktor P. <pohrebnyak@i.ua>]

Hi, aupadras.

I can see that your application has crashed in Message class constructor.
Thing is that std::bad_alloc() exception was thrown before
Message::setString() method got invoked which means that message hasn't even
started parsing the FIX string.

I can only suggest you to run a memory leak detector to see what the problem
is.

Regards,
Viktor



--
View this message in context: http://quickfix.13857.n7.nabble.com/Memory-Allocation-tp6541p6546.html
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.

Re: [Quickfix-developers] Memory Allocation

[Viktor P. <pohrebnyak@i.ua>]

Hi, aupadras.

I've checked your output but it contains nothing suspicious.

Are you sure you do not create an excessive amount of SocketInitiators in
your main loop? Each SocketInitiator creates a DataDictionary instances
which consume a lot of memory so if used without caution they can waste lots
of RAM.

Regards,
Viktor



--
View this message in context: http://quickfix.13857.n7.nabble.com/Memory-Allocation-tp6541p6548.html
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.