The process for identifying memory leaks looks like a real pain in the butt. After thinking about it for a while, I would be perfectly happy to just automatically reboot the server after CPU / Memory are depleted to a certain point.
this is a really bad attitude to take towards your code. not only has matts given you great code which you compliment, but he's given you an outline for advanced debugging techniques he used in the same code you praise.
instead of taking the opportunity to learn more about bugs that might be in your code (and software development in general) from someone who took the time to provide an detailed answer your question, you've decided to throw away his proven advice.
if you feel his advice is over your head, and you would like to learn but don't think you're capable yet, say so. i'm sure other suggestions can be offered, including advice on your follow-up question. as it stands, your dismissive tone leaves me unsympathetic to your current situation.
why would anyone here want to provide you with help in the future if you openly throw away such good advice?
i certainly wouldn't.
~Particle *accelerates*
| [reply] [Watch: Dir/Any] [d/l] |
You should *never* need to reboot the whole server - instead set MaxRequestsPerChild low (axkit.org has it at 100), and install something like Apache::SizeLimit to make sure you don't get one particular process going totally out of control. | [reply] [Watch: Dir/Any] |
I agree with particle on this one. Who is to say that tomorrow you won't write another script with exactly the same problem your current one has? In that case, your server resources will become depleted twice as fast without an end in sight. Also, why be satisfied with code that you know is broken?
thor | [reply] [Watch: Dir/Any] |