note 22969 deleted from function.fbsql-free-result by spic
| From: | spic@php.net | Date: | Wed, 28 Aug 2002 11:30:39 +0000 |
| Subject: | note 22969 deleted from function.fbsql-free-result by spic | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-35898@lists.php.net to get a copy of this message | ||
As stated above, this function appears to be of critical importance. If you are experiencing random
hangs and crashes in your scripts, suspect a lack of fbsql_free_result().
It appears that failure to explicitly release a result set causes memory problems, usually
manifested by Apache segfaulting. With FrontBase < 3.4, this caused us very serious problems as
locks were not being released, resulting in a stalled database. With 3.5, this no longer happens,
but nonetheless the httpd child dies, which means that pages are only partially output, and also
impacts on performance. I don't know the internals of the fbsql PHP driver and don't have
time to investigate further. Simply using fbsql_free_result() without knowing exactly what is
causing the problem might look like voodoo, but in my experience it is voodoo that works.
David Gillies
San Jose
Costa Rica