Right, its Sun OS 5.6, MySQL 3.22.20a, and PHP 3.0.6. I think the problems
are caused by not adding a free statement at the end of the scripts, but I
thought PHP did a pretty good job of clearing up after itself...
----- Original Message -----
From: Sasha Pachev <sasha@stripped>
To: Adam Powell <adam@stripped>
Cc: <php3@stripped>; <mysql@stripped>
Sent: 24 April 1999 15:26
Subject: Re: one more thing
> Adam Powell wrote:
> > Sorry about this, before I forget I have one more question. We run an
> > network that consists of PHP pages linking to a mySQL database. We have
> > upgrade to Oracle because basically mySQL cannot hack the number of ads
> > we are serving, however this is waay in the future. Currently something
> > causing a memory leak in the database, our 450 keeps going up to 999 Meg
> > used (the mySQLd process that is) and then starts swapping and the techs
> > have to restart it.
> > We use queries such as
> > $res = mysql("dbname", "SELECT * FROM personal WHERE
> > $d = mysql_fetch_object($res);
> > mysql_free_result($res);
> > echo "Welcome $d->first_name $d->second_name";
> > Can anybody tell me any possible reasons, or things to watch out for,
> > may be causing any memory leaks? There are a LOT of pages like the one
> > above, and I think that something fundamentally wrong is happening in
> > them.
> > Thanks again,
> > Adam
> What OS are you using? Good possibility that you have memory leaks in
> libc itself, but I am not sure. I've never heard of any memory leaks in
> MySQL itself.
> Sasha Pachev