Bug #17323
closedOut of memory in random php-scripts
0%
Description
Environment: Windows 2003 server, Apache 2.2.4, php 5.2.1 (problem was the same with 5.2.2), MySQL 5.0.27.
This error is fatal and occurs only while working in BE. It seems to
occur whenever a change is made. This could be uploading images, moving an element, writing inside an element, or simply clicking on an extension.
I can see no consistency in the errors, other than the above, but
then I do not have a thorough knowledge of the code behind.
Tried to downgrade PHP version (to 5.2.1), without a change. This error seems to lock up the apache server, and after restarting Apache service everything is fine (until next time) , MySQL seems unaffected and does not need restarting.
I have several sites running on this server, some of which were moved from a temporary WAMP installation. (With Typo3 version 4.0)
The error did not occur on that installation, but now occurs for moved
sites as well as new ones.
See additional information for error-extracts.
[Tue May 22 15:00:26 2007] [error] [client 83.136.92.160] PHP Fatal error: Out of memory (allocated 4194304) (tried to allocate 24576 bytes) in C:\\TYPO3_4.0.2\\Apache\\std\\kkpi\\t3lib\\class.t3lib_befunc.php on line 3009, referer: http://kkpi.kinavej.dk/typo3/alt_doc.php?&returnUrl=%2Ftypo3%2Fsysext%2Fcms%2Flayout%2Fdb_layout.php%3Fid%3D8&edit[tt_content]74=edit
[Tue May 22 15:00:31 2007] [error] [client 83.136.92.160] PHP Fatal error: Out of memory (allocated 524288) (tried to allocate 393216 bytes) in C:\\TYPO3_4.0.2\\Apache\\std\\kkpi\\typo3\\sysext\\cms\\layout\\db_layout.php on line 722, referer: http://kkpi.kinavej.dk/typo3/alt_mod_frameset.php?fW=260&nav=/typo3/alt_db_navframe.php%3F&script=sysext%2Fcms%2Flayout%2Fdb
[Wed May 23 10:02:10 2007] [error] [client 83.136.92.160] PHP Fatal error: Out of memory (allocated 11796480) (tried to allocate 98304 bytes) in C:\\TYPO3_4.0.2\\Apache\\std\\kkpi\\t3lib\\class.t3lib_loadmodules.php on line 450, referer: http://kkpi.kinavej.dk/typo3/alt_doc.php?&returnUrl=%2Ftypo3%2Fsysext%2Fcms%2Flayout%2Fdb_layout.php%3Fid%3D8&edit[tt_content]78=edit
[Wed May 23 10:02:19 2007] [error] [client 83.136.92.160] PHP Fatal error: Out of memory (allocated 1572864) (tried to allocate 98304 bytes) in C:\\TYPO3_4.0.2\\Apache\\std\\kkpi\\t3lib\\config_default.php on line 271, referer: http://kkpi.kinavej.dk/typo3/
[Wed May 23 10:02:20 2007] [error] [client 83.136.92.160] PHP Fatal error: Out of memory (allocated 1572864) (tried to allocate 98304 bytes) in C:\\TYPO3_4.0.2\\Apache\\std\\kkpi\\t3lib\\config_default.php on line 271, referer: http://kkpi.kinavej.dk/typo3/
[Wed May 23 10:02:23 2007] [error] [client 83.136.92.160] PHP Fatal error: Out of memory (allocated 1572864) (tried to allocate 98304 bytes) in C:\\TYPO3_4.0.2\\Apache\\std\\kkpi\\t3lib\\config_default.php on line 271, referer: http://kkpi.kinavej.dk/typo3/
[Wed May 23 10:02:24 2007] [error] [client 83.136.92.160] PHP Fatal error: Out of memory (allocated 1572864) (tried to allocate 98304 bytes) in C:\\TYPO3_4.0.2\\Apache\\std\\kkpi\\t3lib\\config_default.php on line 271, referer: http://kkpi.kinavej.dk/typo3/
[Wed May 23 10:02:29 2007] [error] [client 83.136.92.160] PHP Fatal error: Out of memory (allocated 1572864) (tried to allocate 98304 bytes) in C:\\TYPO3_4.0.2\\Apache\\std\\kkpi\\t3lib\\config_default.php on line 271, referer: http://kkpi.kinavej.dk/typo3/
[Wed May 23 10:58:36 2007] [error] [client 83.136.92.160] PHP Fatal error: Out of memory (allocated 524288) (tried to allocate 98304 bytes) in C:\\TYPO3_4.0.2\\Apache\\std\\kkpi\\typo3\\init.php on line 103, referer: http://kkpi.kinavej.dk/typo3/alt_doc.php?returnUrl=db_list.php%3Fid%3D8%26table%3D&edit[tt_content][-90]=new
(issue imported from #M5668)
Updated by Steffen Kamper over 17 years ago
AFAIK php 5.2.0 - 5.2.2 has much bugs, most with memory management. So i think this is a php issue.
Try same script with 5.1.x or attach the script to let it check.
Updated by Jacob Johannessen over 17 years ago
Downgrading PHP version to 5.1.6 solved the problem definitively. Server
has been running stable for three weeks.
Thank you for the quick reply.