Are you disposing the results of each select call? Not being familiar with Python, as well as not knowing which interface for Python you are using, or the code used to invoke the selects, I can only surmise that the result data from each select is being stored in RAM and never garbage collected. At least that could be responsible for significant memory jumps. For small jumps, it could simply be the accumulation of multiple objects. So 1) you may have to explicitly destroy result data and 2) you may need to ensure that you are re-using the same object.
Without more info, any guess is as good as another. Keary Suska Esoteritech, Inc. "Leveraging Open Source for a better Internet" > From: Stephen Robert Norris <[EMAIL PROTECTED]> > Date: 16 Oct 2001 22:00:35 +1000 > To: [EMAIL PROTECTED] > Subject: [GENERAL] Python interface memory leak? > > Does the python interface leak memory? We are seeing the process grow > with basically every select. Any suggestions on what's going on? There > are no cycles, and a trivial program (basically a loop around a select) > demonstrates the problem. > > This is 7.1.2 on RH7.[01]. > > Stephen > ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
