On Jan 24, 2005, at 1:14 PM, Dossy Shiobara wrote:

I'm starting to suspect that the "leak" is in application (Tcl) code,
and not in the core AOLserver.  I could be wrong, but signs are
starting
to really point in that direction.

Don't forget I wasn't the only person to report this.

Can you share the code with me so I can examine and review it?

I will ask the client.

Are there any errors being thrown to the error log?  If there's some
memory cleanup steps towards the end of the script that aren't being
executed because of an earlier uncaught Tcl error, that's a usual
culprit in these kinds of problems.

No, there aren't, and there's no memory handling in this script at all. As I said it's very simple - select a bunch of data from the database and return the page.

I have not yet updated Tcl, and still plan to do that.

So, you're running the same version of Tcl for your 3.3ad13 and the 4.0.8 builds? Does that mean you're running Tcl 8.3.2 with AOLserver 4.0.8? I'd strongly suggest building Tcl 8.4.9 with AOLserver 4.0.10 and seeing if that has any impact whatsoever on the memory growth.

No, I'm running Tcl 8.4.6 with 4.x. I'll try updating, but that's not all that old.

What else can I do to help track this down?

At this point, I think a code review is in order to identify if there's any places where the application could be using memory that never gets cleaned up or freed. If your application uses tDOM and you're not extra-careful about placing [catch]'es around blocks of code to ensure that the appropriate tDOM cleanup happens, this is a very common place for applications to leak memory. If you use NSVs and allow them to grow without bound, this is another common way to leak memory.

I don't use tDOM, in fact it's not even installed on this system. I don't believe my code uses any NSVs either, but they are probably in use in the ACS code.

I'm using a very old version of ACS here - 4.2, the last non-Java
version Arsdigita released.  But Dan, who reported this first, was
using OpenACS.  That has been changed so much it's virtually no longer
the same code-base.

janine


-- AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> 
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Reply via email to