On 2005.01.24, Janine Sisk <[EMAIL PROTECTED]> wrote: > > 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.
I suspect the issue Dan's observing has a different cause than what you're seeing. Can someone do a control experiment and set up a vanilla ACS 4.2 with no customizations whatsoever and hit it with a bunch of traffic and see if the memory stays stable or grows indefinitely? If on a vanilla ACS 4.2 install, the memory footprint reaches a stable size and doesn't grow indefinitely, it might be a better indicator that the problem with the memory growth is most likely caused by a customization you've added to your code. On the other hand, if it leaks even with a vanilla ACS 4.2, while it doesn't rule out bad application code, I can at least review the ACS code even if your client doesn't want to share your customized code. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- 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.
