PHP ERROR [1] Allowed memory size of 67108864 bytes exhausted (tried to allocate 47188648 bytes) in sources/files2.php on line 104

On the index.php?page=start I get the following

Critical error – bailing out

93  94  95  96  97  98  99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123

function cache_and_carry($func, $args, $timeout = null) {     global $HTTP_DOWNLOAD_MIME_TYPE, $HTTP_DOWNLOAD_SIZE, $HTTP_DOWNLOAD_URL, $HTTP_MESSAGE, $HTTP_MESSAGE_B, $HTTP_NEW_COOKIES, $HTTP_FILENAME, $HTTP_CHARSET, $HTTP_DOWNLOAD_MTIME;     $ret = mixed();     $path = get_custom_file_base() . '/safe_mode_temp/' . md5(serialize($args)) . '.bin';     if (is_file($path) && (($timeout === null) || (filemtime($path) > time() - $timeout * 60))) {         $_ret = cms_file_get_contents_safe($path);         if ($func == 'http_download_file') {             $ret = @unserialize($_ret);         } else {             $ret = $_ret;         }     } else {         $_ret = call_user_func_array($func, $args);         require_code('files');         if ($func == 'http_download_file') {             $ret = array($_ret, $HTTP_DOWNLOAD_MIME_TYPE, $HTTP_DOWNLOAD_SIZE, $HTTP_DOWNLOAD_URL, $HTTP_MESSAGE, $HTTP_MESSAGE_B, $HTTP_NEW_COOKIES, $HTTP_FILENAME, $HTTP_CHARSET, $HTTP_DOWNLOAD_MTIME);             if ($_ret !== null) {                 cms_file_put_contents_safe($path, serialize($ret), FILE_WRITE_FAILURE_SOFT | FILE_WRITE_FIX_PERMISSIONS);             }         } else {             $ret = is_string($_ret) ? $_ret : serialize($_ret);             cms_file_put_contents_safe($path, $ret, FILE_WRITE_FAILURE_SOFT | FILE_WRITE_FIX_PERMISSIONS);         }     }     return $ret; }

Hello,

Thanks for the report. Our lead developer is extremely busy at the moment but I am sure this issue will be looked at in the next couple of weeks.

Regards,
Adam

Hi,

I'm sorry you didn't receive a timely response to this topic.

Thank you for showing the affected code clearly in your report here.

This is a really odd issue.

Tracing the code, the only possibility I could see was this 0004843: Large oEmbed responses should not be accepted - Composr CMS feature tracker - and this seems very unlikely to happen in practice.
I suppose if you were very unlucky and reference a site with a buggy oEmbed endpoint it could happen.

To answer your direct question, the memory limit can be increased via an unofficial option in Commandr (Admin Zone > Tools > Commandr, assuming you have it installed).

Type this command exactly (it needs the leading colon, trailing semicolon, and it is M not MB):


This would set a limit of 128MB on the server, which hopefully would be enough.

However, really nothing should be trying to pull a file over 64MB out of the HTTP cache on the home page. So while this may get rid of the error, it should never get into this situation in the first place.

I'd try manually editing the pages/comcode_custom/panel*.txt and pages/comcode_custom/start.txt files to remove stuff temporarily until you can trace the cause, and then come back to me on it. If you'd like me to personally investigate drop me an email, chris@ocproducts.com.

I apologise again for this being a very late reply. I had no ability to do support for the last 3 months, and this is a very technical development issue.

Best,
Chris