Fatal error: Allowed memory size of….
-
Hello
I get this message when trying to open in new window more that one page:Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 2211214413203 bytes) in C:\wamp64\www\wp-includes\functions.php on line 5231
The amount of bytes seems to be huge! Any solutions?
Thank you!
-
What were you opening when you got that error? What’s the PHP memory setting?
Your site is trying to do something that uses up more memory than your current PHP memory limit is set to. You can try fixing the plugin, looking at your error log etc. Or you can also try increase your memory limit. This link shows you how to do that:
https://www.wpbeginner.com/wp-tutorials/fix-wordpress-memory-exhausted-error-increase-php-memory/Hello, try this:
Amending Your wp-config.php File
First, try to edit the wp-config.php file on your WordPress site. It is located in your WordPress site’s root folder.
Edit this file, for example with the command:
sudo nano /var/www/html/wp-config.php
Next, you need to paste this code in wp-config.php file just before the line that says ‘That’s all, stop editing! Happy blogging.’
Define(‘WP_MEMORY_LIMIT’, ‘256M’);https://i.gyazo.com/43fbb44d266796a981cd3b3767f0d3cb.png
This code tells WordPress to increase the PHP memory limit to 256MB.
You can customize the number to increase the memory limit to a higher amount if you wish. Then you need to save changes and upload your wp-config.php file back to your server.
You can visit your WordPress site and memory exhausted error should disappear now.
If the error is still occurring, you may need to increase the WordPress memory limit to a higher number.or this as well
Updating Your php.ini File
If you use cPanel, move to the Files and click on the File Manager button. Make sure the checkbox for Show Hidden Files is checked and then press Go.
Select your wp-admin folder and find a file php.ini or php5.ini. If you can’t find it, create one by clicking the New File button in the top left-hand corner. Name the file php.ini and click Create File button on the pop-up.
If you made everything right, but it still doesn’t work, try to rename the file to php5.ini. Open the file, add or edit the following lines. After it press save and close.upload_max_file_size = 100M
post_max_size = 200M
memory_limit = 300M
file_uploads = On
max_execution_time = 180Change the 100M, 200M and 300M limit to the value you require.
Changing the value of max_execution_time will limit the amount of time spent loading a script in seconds.
Generally, the values you enter should increase from top to bottom 100-200-300.
The upload_max_filesize value should be the smallest, post_max_size is medial and memory_limit should be the largest.
Before to check the result, clear your browser’s cache.and this
Editing Your .htaccess File
If aditing of php.ini file doesn’t work, try to edit .htaccess file and add/edit the following code at the bottom:
php_value upload_max_filesize 100M
php_value post_max_size 200M
php_value memory_limit 300M
php_value max_execution_time 180
php_value max_input_time 180Code changes are similar to your php.ini file. Put the limits value you require. Save when you’re done and clear the cache for your browser.
I believe the huge memory leak is linked to changes to wp-includes/functions.php in WordPress 4.9.7 update, specifically this function on line 5233:
function wp_is_stream( $path ) {
$wrappers = stream_get_wrappers();
$wrappers_re = ‘(‘ . join(‘|’, $wrappers) . ‘)’;return preg_match( “!^$wrappers_re://!”, $path ) === 1;
}function wp_is_stream( $patWe have been encountering the same issues all morning, and at one point it was trying allocate millions of terabytes of memory – which is completely abnormal.
Clearly none of the of the standard memory increase fixes suggested in this thread are going to help in the case described by @terrox – (2211GB) or in the case of @breakoftheec on this thread: https://www.ads-software.com/support/topic/wp_is_stream-crashing-the-server/ (2620GB)
We have temporarily resolved by reverting back to WordPress 4.9.6, but this ideally needs flagging up to the WordPress developers.
This is actually an old elusive bug https://bugs.php.net/bug.php?id=72451 that is most likely associated with the use of a Windows server.
I see it from time to time on my sites, but after the last update, sites really began to fall almost constantly, so I had to “patch” the wordpress files as a temporary measure.My environment
Windows Server 2008 R2
PHP 7.1.18
Apache/2.4.28 (Win64) OpenSSL/1.0.2lNot windows – limited. On LAMP (PHP 7.1.19) it is the same. once increased limits to 256 just part of requests get that error.
Same issue with my site – wordpress is trying to allocate hundreds of terabytes. I host it on Linux. The site is randomly not loading.
Most probably related to what the
stream_get_wrappers()
array returns more than anything to do with memory allocation. For those of you who are experiencing this, if you could print the contents of that array it may help in finding a solution.I’ve been having this problem as well. It only seems to appear under heavy load.
I initially put the problem down to having switched from PHP 7.2 to 7.1 (for reasons unrelated to WordPress) and possibly having a corrupt installation, but it seems to do it under 7.0 as well and now I think I just didn’t spot it under 7.2 and the problem is with PHP 7.x in general. (It wasn’t a problem with 5.x running under IIS).
I’m currently running PHP 7.0 running as a module under Apache 2.4 on Windows. Here’s one of the numerous entries I’m getting:-
[27-Jul-2018 16:17:23 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 7234872724905026747 bytes) in C:[OUR WORDPRESS FOLDER]\wp-includes\functions.php on line 5237
You can see that the amount of memory it tried to allocate is beyond ludicrous.
I too thought that the problem was with stream_get_wrappers() since that’s where the problem was occurring, but that bit appears to work, and the contents of the array was something like
(php|file|glob|data|http|ftp|zip|compress.zlib|https|ftps|phar)
IIRC the problem appears to occur when it gets to the line
$wrappers_re = ‘(‘ . join(‘|’, $wrappers) . ‘)’;
(Sorry, I did this quick-and-dirty debug check before I saw your post, and I didn’t keep all the details).
- This reply was modified 6 years, 4 months ago by Raspberryade.
It looks like this issue has been addressed in the upcoming (in a couple of days I believe) release of 4.9.8.
https://core.trac.www.ads-software.com/ticket/44532@te_taipo ; That’s great, thank you for bringing it to my attention.
So, from what I can tell, this *is* a PHP bug (in 7.0 and 7.1 and possibly fixed in 7.2, though I can’t switch to that…)
I ended up using bezpeka.com’s short-term solution here (one of the other methods didn’t work for me):-
https://www.ads-software.com/support/topic/wp_is_stream-crashing-the-server/#post-10470012
That’ll probably do it until 4.9.8 gets officially released.
Thanks again!
Great stuff. bezpeka’s should do the trick for now, yes.
I get this error when I try to update WP. How can I update?
Hello
I get this message when trying to edit in Shop to add “BEST SELLER”. The ERROR is:
FATAL ERROR:Out of memory (allocated 88342529) tried to allocate 573773 bytes) in /home1/xxxxxxx/public_html/wp-imcludes/class.wp-scripts.php on line 413
And I don′t have too many pages!!PAGES
Shop — Front Page, Shop Page
Edit | Quick Edit | Trash | ViewThanks for your help!!!
- The topic ‘Fatal error: Allowed memory size of….’ is closed to new replies.