RE: Session's memory

Hi, rotor (Leonid ?) The first thing to do is to investigate the session's memory structure using onstat -g afr SESSION_ID There is a chance that that the memory leak is caused by the server bug... but I'm quite sure that memory leak is caused by the VERY poor application design. Just take a look at the output: the momory allocation occurs only when the session's current cursor name (like: CRS_1348, CRS_1362) increments. That means, that, most probably, the application doesn't deallocate the cursor or prepared SQL statement, and simply creates more and more cursor's and/or prepared SQL statements. -Alexey > -----Original Message----- > From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] On > Behalf Of rotor > > Hi community! > Who knows in which circumstances server allocates memory for a > session? I have 'onstat -g ses 183 -r 1' output during 10 minutes. I > don't see any criminal there. Except one - memory. It grows up to 400 > Mb per 10 min! 20 sessions like this one and... You understand. So, > send to you this output with hope to hear your comments and > appreciations. sending to informix-list