#2981 - Allowed memory size
-
By Paul Flavel
- Added
- 5 views
| Identifier | #2981 |
|---|---|
| Issue type | Major issue (breaks an entire feature) |
| Title | Allowed memory size |
| Status | Completed |
| Handling member | Chris Graham |
| Addon | General / Uncategorised |
| Description | I am currently running release 25, trying to upgrade to 27. But on the upgrader.php page i am getting the following error.
Critical error – bailing out This is an error that has been elevated to critical error status because it occurred during the primary error mechanism reporting system itself (possibly due to it occurring within the standard output framework). It may be masking a secondary error that occurred before this, but was never output - if so, it is likely strongly related to this one, thus fixing this will fix the other. Allowed memory size of 67108864 bytes exhausted (tried to allocate 528384 bytes) [sources/global.php(251) : eval()'d code at 163] Details here are intended only for the website/system-administrator, not for regular website users. » If you are a regular website user, please let the website staff deal with this problem. This issue appears when I enter the upgrader page. I am running on a centos vps with php version 7.0.14 (tried earlier versions as well, same error}. Allocated 256M allowed memoryn{tried 512M as well, same error}. 2GB Swap. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
If you run "sh decache.sh" before launching the upgrader (i.e. from a bash console) it will fix it. Or you can delete all the files from the themes/*/templates_cached/* directories.
The issue is that the last RC regenerates CSS and JS when the cache is emptied, but some servers use more RAM to do that, and some sites have more files - so many users have had memory issues for the limit we define.
Thankyou