Of course, the short term fix, is to lower MaxRequestsPerChild which
will hopefully reduce the leakage but won't help performance.
Leaks in DBD::Oracle and Oracle's own libraries are not entirely rare.
You should send your simple, stand-alone example to the dbi-user's
mailing list with your exac
Has anyone else come across a problem using DBD::Oracle, where
connect() leaks approximately 80k every time it is used (which, in my
case, is with every request child processes handle)? It's negligable with
regular perl scripts, but I've seen child sizes grow to 40 megs before I
killed them all.
