I often have Critical Errors with Memory Limit issue. I have set:

memory_limit = 1024M

for in Direct Admin panel which is the max value allowed there.

But the memory limit still happens quite often when creating or updating posts at WP Admin backend.

How can I solve this consistent issue?

Appreciate any advice.

Cheers

These error only if i want to edit post/pages. I tried a lot of tutorial for increasing memory limit, but still error

Please help…

Regards

I was having trouble to use your plugin as i was trying to export all orders at once. Though my hosting had around 2GB memory_limit set, it was always failing at 512M.

Finally after inspecting the plugin code. I found you have hardcoded the memory_limit to 512M in \classes\formats\class-woe-formatter-xls.php file at line number 259.

			//more memory for XLS?
			ini_set( 'memory_limit', '512M' );

Maybe you can come up with a better idea on this ?

I really like the plugin because you can tune a lot of things to improve the usability which other optimizers lack. (Esp. FCP and LCP optimizations).

But on a clients’ site the memory usage gets multiplied by 10 if I turn on Hummingbird. I go from like 45MB to 450MB for each page request. Upgrading the memory_limit helps but quite regularly the infamous “memory exhausted” fatal error occurs. And I think 500MB for a memory_limit is not efficient and maybe can cause stability problems.

Are there any known plugin/theme conflicts which are causing this?

Thanks!

When trying to open the WP Mail SMTP-page, the page loads for a while and then returns the error message: “The link you followed has expired – please try again”. I read somehwere this might have to do with memory_limit being to low, but the issue remains with limit increased to 256MB.

The error log shows the two issues below. Can you shine a light? Thanks!

Ivan

[host website.nl] Backend log: WordPress databasefout Lost connection to MySQL server during query bij query SELECT option_value FROM wo_options WHERE option_name = ‘activate_comments’ LIMIT 1 gemaakt door require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), include_once(‘/plugins/thrive-comments/thrive-comments.php’), tcm, Thrive_Comments::instance, Thrive_Comments->__construct, Thrive_Comments->includes, Thrive_Comments->include_tcb, Thrive_Comments_Settings->tcm_get_setting_by_name, get_option\n, referer: https://website.nl/wp-admin/post.php?post=7666&action=edit

[host website.nl] Backend log: WordPress databasefout Lost connection to MySQL server during query bij query SELECT option_value FROM wo_wlm_options WHERE option_name=’isenable_log’ LIMIT 1 gemaakt door require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), include_once(‘/plugins/wishlist-member/wpm.php’), require_once(‘/plugins/wishlist-member/legacy/init.php’), WishListMemberPluginMethods->LoadInitFile, include_once(‘/plugins/wishlist-member/legacy/lib/integration.shoppingcart.infusionsoft.init.php’), WLM_INTEGRATION_INFUSIONSOFT_INIT->__construct, WishListMemberCore->GetOption\n, referer: https://website.nl/wp-admin/post.php?post=7667&action=edit

What is missing there is WP_MEMORY_LIMIT. I found out that this constant is not defined within class WP_Debug_Data in wp-admin/includes/class-wp-debug-data.php.

I wonder if there’s a reason for that? This seems to be an important constant, too.

“The settings for post_max_size and upload_max_filesize are not the same, this could cause some problems when trying to upload files.”

I don’t even know where the settings for both are, so I have no idea how to make them the same. I’m hoping somebody here can help. Thank you.

ERROR: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 5242912 bytes)

…but at least the file got uploaded to S3.

I have a CSV import script running via server cron but Wordfence seams to be causing issues with it. PHP-cli has an unlimited memory_limit => -1 however with Wordfence enabled, this is restricted to 128MB.

I think I’ve tracked it down to line 38 of wordfence.php where you cast the memory limit to an int.

if((int) @ini_get('memory_limit') < 128){
    if(strpos(ini_get('disable_functions'), 'ini_set') === false){
	@ini_set('memory_limit', '128M'); //Some hosts have ini set at as little as 32 megs. 64 is the min sane amount of memory.
    }
}

In my case, -1 is less than 128, theoretically and and thus Wordfence sets a new limit which in turn actually restricts it.

Should there not be an additional check here to see if the memory_limit is -1 or if the current server api is cli php_sapi_name() !== 'cli'

I’m receiving the following error:

[25-Feb-2019 15:15:47 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 268435464 bytes) in /var/www/html/blog/wp-includes/compat.php on line 181

At first I thought it had something to do with the PHP_Memory_Limit but I already raised it from 64 to 128mb then to 256mb and now to 512mb. The result remains the same and I still get the error messages. The difference is the amount it is trying to allocate. As I raise the limit so does the tried to allocate part.

In this example I had set the php_memory_limit to 256mb
[12-Feb-2019 05:15:48 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 134217736 bytes) in /var/www/html/blog/wp-includes/compat.php on line 181

Does someone have a clue about what is causing this?