|
From: Karl O. P. <ko...@me...> - 2007-08-06 14:40:57
|
On 08/05/2007 01:41:10 PM, Lionel Bouton wrote:
> Here
>
> is what I think happens:
>
> InactiveDestroy => 1 is used to support asynchronsous cleaning of the
> DB
> (which is quite buggy, I never understood why and still recommend to
> leave it deactivated unless it really stalls the server too long and
> asynchronous cleaning actually works for you). InactiveDestroy is
> meant
> to prevent the database handle from being destroyed when it goes out
> of
> context (which happens when you fork and open a new database
> connection
> for example). I believe that this InactiveDestroy could be extended to
>
> the prepared statements (probably erroneously, it doesn't make sense
> for
> me to do so), which would explain the leak.
>
> I'll simply remove InactiveDestroy => 1 when asynchronous cleaning
> isn't
> active, this should help (and shouldn't have any bad side-effect).
Tentively, after running for one night, 1.6.8 seems to have
made the leak go away. Yay.
I'll report back again in a week or so.
Karl <ko...@me...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
|