The direct cause of the leak is that OCIInitialize is called with OCI_THREADED in 7.4 and later. Are things likely to go bonkers if that flag is removed? Do you still remember why you added it? (In 7.2 that flag is used only if ORACLE_USE_THREADS isn't defined.)
/ Martin Stjernholm, Roxen IS
Previous text:
2004-10-02 18:42: Subject: memory leak in oracle module
My experience with the Oracle libraries is that they SUCK. Mostly they suck if you try to use them with threads. You might want to try different version of the oracle client libraries, because I had different problems with different versions when I originally implemented the oracle module. (8.0.5.something worked really well for me.. :)
Apparenly Pike is the only application in existance which uses the dynamic callbacks in the oracle library, and that particular API doesn't seem to be tested before Oracle releases their software... :(
/ Fredrik (Naranek) Hubinette (pappa)