quickfix-developers

[Quickfix-developers] Memory leaks for Initiator

[Quek T. W. <qt...@ya...>]

 Hi,
    
    i am currently porting and testing a production quickfix app  from Solaris to AIX 5.2.  The version of quickfix used is 1.10.2  and compiler is VisualAge C++ 6.0
  
    My tests consists of : 
  
     1)  Fix client ( SocketInitiator )
          a)  continuously sends Fix42::NewOrderSingle every second
          b)  receives the execution reports.  Prints out the message
         and does no further processing.
  
     2)  Fix server (SocketAcceptor) 
         -  accepts the fix messages from the client and returns
         execution report.
  
    What i observed is that the Fix client memory usage goes up and
  eventually it will crash.   The Fix server is stable and there is no
  memory leak.
  
  I read a recent post here on "ThreadedSocketConnection: fix for memory  growth under heavy load".    Will the use of the  SocketInitiator class also result
  in some sort of memory leak ?   Should i switch to the ThreadedSocketInitiator
  instead ?
  
  
  thanks,
  
    Quek Tai Wee
  

		
---------------------------------
 Yahoo! Music Unlimited - Access over 1 million songs. Try it free.

[Quickfix-developers] re:Memory leaks for Initiator

[<lar...@su...>]

Hello, while using the QuickFix JNI Wrapper I encountered an memory
error using Initiator

=20

The problem occurred in xstring on line 601 : in function _Myt&
assign(const _Myt& _Right,

                      size_type _Roff, size_type _Count)

=20

=20

else if (_Grow(_Num))

                                 {          // make room and assign new
stuff

                                 _Traits::copy(_Myptr(), _Right._Myptr()
+ _Roff, _Num);

                                 _Eos(_Num);

=20

=20

=20

The thread 'Win32 Thread' (0x258) has exited with code 0 (0x0).

First-chance exception at 0x6d68089d in java.exe: 0xC0000005: Access
violation writing location 0x003c0f98.

Unhandled exception at 0x6d68089d in java.exe: 0xC0000005: Access
violation writing location 0x003c0f98.

The program '[3260] java.exe: Native' has exited with code 0 (0x0).

=20

=20

=20

Lars Mattsson =20

=20

Re: [Quickfix-developers] re:Memory leaks for Initiator

[Oren M. <or...@qu...>]

Do you have a stack trace?

--oren

lar...@su... wrote:

> Hello, while using the QuickFix JNI Wrapper I encountered an memory 
> error using Initiator
>
>  
>
> The problem occurred in xstring on line 601 : in function _Myt& 
> assign(const _Myt& _Right,
>
>                       size_type _Roff, size_type _Count)
>
>  
>
>  
>
> else if (_Grow(_Num))
>
>                                  {          // make room and assign 
> new stuff
>
>                                  _Traits::copy(_Myptr(), 
> _Right._Myptr() + _Roff, _Num);
>
>                                  _Eos(_Num);
>
>  
>
>  
>
>  
>
> The thread 'Win32 Thread' (0x258) has exited with code 0 (0x0).
>
> First-chance exception at 0x6d68089d in java.exe: 0xC0000005: Access 
> violation writing location 0x003c0f98.
>
> Unhandled exception at 0x6d68089d in java.exe: 0xC0000005: Access 
> violation writing location 0x003c0f98.
>
> The program '[3260] java.exe: Native' has exited with code 0 (0x0).
>
>  
>
>  
>
>  
>
> *Lars Mattsson*  
>
>  
>