I have a memory leak and am having no luck at finding it.
Let me first tell you a sordid little story that will set this up.
I am running a Virtuosso VE with whm / cpanel provided by a vendor in his operating center.
I was on a VE where everything was running just fine.
My vendor migrated me to a new box with the latest and greatest version of Virtuosso (I didn't ask for the migration, but that is a different story.)
As far as I know, everything was fine at that point (although, it is possible that I didn't notice the problem at that point)
I went into root whm and there was an Apache Security notice. So, I recompiled to fix the security leak. The recompile did not work correctly and my vendor had to fix it.
Since then, I now have a memory leak that runs out the private memory (privvmpages) after a few hours.
Now:
I think that it is a either a problem with the new Virtuosso or it is a problem caused by the recompile for the security leak. It could be a problem between my code and the new environment.
My vendor says that it is a problem with my code. The only stuff on this server are some applications intalled by Fantastico, some html stuff, and a couple of php scripts I wrote using an XML RPC library.
My vendor tells me that the memory leak is my problem - which I think is far from clear.
But, I cannot demonstrate the truth or falsity of this claim because I have been unable to determine the source of the memory leak.
(I am a highly experienced and competent programmer, but, not in this environment)
My vendor tells me there are no tools for diagnosing this.
So, what I'd like is a suggestion of an approach to diagnosing this problem.
Are there no utilities that can track memory allocations (by, time and script, or something) so that I can see what is going on.
I've looked at top, but, I don't see anything that makes any sense to me.
Does anyone have any suggestions of an approach to this problem?
Thanks in advance for any suggestions.
Geoff



LinkBack URL
About LinkBacks
Reply With Quote
My initial reaction would be a problem either with Virtuozzo or their stup of it, as memory leaks are quite unlikely.




