Description: ------------ it exist a memory leak using mdb2 driver with db_dataobject. Using singleton design pattern. I use this, in a shell script writed in php. this is not solved using ->free(); Test script: --------------- I create an object that have a db_dataobject object, when I unset/null my object, the memory doesn't go down. Expected result: ---------------- The same memory usage than before object creation should be expected after the destruction. Actual result: -------------- Allowed memory size of 16777216 bytes exhausted (tried to allocate 6245 bytes)

I have more information from it : print_r("=============>"); print_r($this->_Tdb); $this->_Tdb->free(); print_r("=============>"); print_r($this->_Tdb); will print this : =============>DataObjects_List Object ( [__table] => list [id] => 272 [name] => myname [_DB_DataObject_version] => 1.8.8 [N] => 1 [_database_dsn] => [_database_dsn_md5] => 5678f7a9afce314fbc8263ec8ea6c43c [_database] => db1 [_query] => [_DB_resultid] => 15 [_resultFields] => [_link_loaded] => [_join] => [_lastError] => ) =============>DataObjects_List Object ( [__table] => list [id] => 272 [name] => myname [_DB_DataObject_version] => 1.8.8 [N] => 1 [_database_dsn] => [_database_dsn_md5] => 5678f7a9afce314fbc8263ec8ea6c43c [_database] => db1 [_query] => [_DB_resultid] => 15 [_resultFields] => [_link_loaded] => [_join] => [_lastError] => ) so it generate looping error, that generate too much data in memory. The error is that I can't make two queries on the same object, but i make a free and it doesn't clean. Any idea ?

commenting the if at the line 392 resolve the problem. I think it does not get the case of a "->get()" after a ->find();

Nahuel, can you provide a small test case for this bug please?

Not easy to provide something. I think we can do something like : <?php $db =& DB_DataObject::factory("myTable"); $db->myfield = "myvalue"; $rownb = $db->find(); $db->free(); $db->get('2); print_r($db); There is an error that say two request cannot be done on the same object. ?>

We are experiencing the same issue. However we have noticed the following: 1) The error does not occur if the object is created without calling ->insert() and ... 2) using ->link() at the same time. 3) If two instances of the script are launched at the same time, they will both insert the same number of record (failure in our case if occurring at 10922 and two scripts insert double that number exactly even though they are launched at the same time). 4) The error in our case is returning: Glibc detected ... After setting MALLOC_CHECK_=0 The error became: Segmentation Fault Hope this helps, Hedge

ok can you * call free() after finishing a transaction. * be carefull if using get->link() - it may not do any free'ing.. - in which case you may manually have to modify the $GLOBALS[DB_DATAOBJECT] array to free any extra data. * do not re-use objects * check the size of $GLOBALS[DB_DATAOBJECT] at various stages of the application to see if it's growing. What free does is call a method in the DB library that cleans up records of insert id's. along with clearing a few cache results. If you are getting segfaults you need to find the page on www.php.net that describes doing gdb backtraces.

use clone() before doing the query rather than doing multiple queries on a single object.