I now made a simple test case with a select query from an rxml page. Still doesn't leak, but if I push many concurrent requests it dumps core on me in OCIHandleFree called from oracle.c:497 (testing on Solaris 8 sparc). That's not good either, but it seems to be unrelated to the issue at hand. Still, what are your experiences with Oracle and concurrent queries?
As for test case, I'd naturally prefer one that is as minimized as possible. What sort of operation causes the leak (connecting, selecting, insert, updates, transactions, etc)? Are concurrent threads involved? Any sort of closer characterstics are useful.
Maybe you can make a replica of your server and use ab to find out which specific page causes the leak and thereby the queries involved?
/ Martin Stjernholm, Roxen IS
Previous text:
2004-09-27 18:05: Subject: memory leak in oracle module
well, what could i exactly provide? website: no problem, server-config also no problem. but without the oracle db not helpful. if its really helpful, i could ask our db-provider for an read-only access. he has also some interest in fixing the problem ...
/ Michael J. Stenitzer