#009300: Memory issue with the updatecontentobjectname.php script due to caching

Description:

The script calls a function which calls another function ( eZContentObject->fetchDataMap ) which caches its result in "$GLOBALS['eZContentObjectDataMapCache']". Because of this the script will use a lot of memory on large databases.

Setting the global variable to null each time solves the problem, see patch.


Environment:

Operating System: linux
PHP Version: 4.4.3 4.4.4
Database and version: MySQL 4.1


Steps to Reproduce:

Run the updatecontentobjectname.php ( update/common/scripts/updatecontentobjectname.php ) on a database with 1000+ objects, and take a look at the memory usage.


- Attachments
updatecontentobjectname_memory_fix.patch (703 b)
[Download] [Permanent Link]
Patch

- Comments

Could this issue also affect other scripts (in the 'update/common/scripts/' directory)?

#250132 by kracker on November 7th, 2006 [Permanent Link]

Acctually, similar problem was already fixed in 'updatemultilingual.php' script (rev. 16202). But if you'll get one more problem like this, please report it as a new bug with link to this issues.

#250501 by Ruslan Lisnyk on November 23rd, 2006 [Permanent Link]

Fixed in
trunk (3.9.0rc2) rev. 17551,
stable/3.8 (3.8.7) rev. 17552,
stable/3.7 (3.7.10) rev. 17553,
stable/3.6 (3.6.12) rev. 17554.

#250496 by Ruslan Lisnyk on November 23rd, 2006 [Permanent Link]

- History
Properties
Type Bug
Priority Medium
Component Misc
Affects 3.6.11
3.7.9
3.8.5
3.8.6
3.9.0alpha1
3.9.0rc1
Fix Versions 3.6.12
3.7.10
3.8.7
3.9.0rc2
Reporter Rune Langseid
Responsible Ruslan Lisnyk
Status 0 Closed
Resolution Fixed
Created October 31st, 2006
Updated November 23rd, 2006
Resolved November 23rd, 2006
 
Navigation [Permanent Link]
Previous Issue
Back to Issues List
Next Issue: #019127
  DB Deadlocks on ezcontentobject_tree when updating subnode