Disabling scheduled backups in the iTSec plugin Settings is the first candidate for resolving memory issues.
dwinden
Thread Starter
Marty
(@bozzmedia)
Thanks dwinden.
I should have noted that I do not use the backup feature in the plugin, scheduled or otherwise. Any other thoughts for what to check? Cheers
If it’s enabled disable File Change Detection and\or Malware Scanning.
Also check the “PHP Memory Usage” in the “System Information” metabox on the iTSec plugin Dashboard page.
dwinden
Thread Starter
Marty
(@bozzmedia)
File change and malware are set to off.
PHP Memory Usage: 40.6 MB
PHP Memory Limit: 256M
is what I have on the dashboard.
Ok.
I’m not familiar with Google Analytics Dashboard for WP plugin. Perhaps it is making us chase a ghost …
Anyway I’m out of options.
dwinden
Thread Starter
Marty
(@bozzmedia)
Thanks for your help dwinden, I’ll take this back to the other plugin dev. Have a good day.
Thread Starter
Marty
(@bozzmedia)
I wanted to share with the devs that this is an issue with the 4.6 version of this plugin, no issues on sites using the 4.5 version, until I upgrade to 4.6. The issues appears to be during the fetching of google analytics data.
The iTSec plugin uses Google Analytics to harvest anonymous features usage data.
However this can be turned on\off on the plugin Settings page:
Allow Data Tracking [X] Allow iThemes to track plugin usage via anonymous data.
Who knows it will help …
dwinden
Thread Starter
Marty
(@bozzmedia)
I gave that a shot and toggled it both on and off, no luck. Thanks for the suggestion.
Thread Starter
Marty
(@bozzmedia)
For anyone else running into issues, particularly with Google Analytics Dashboard for WP, here is a link to the relevant thread over there. https://wordpress.org/support/topic/memory-error-in-console
I’ll report back here if I find resolution.
The “Allowed memory size of 41943040 bytes” part would suggest that there is a memory limit somewhere of 40 MB in effect …
This bugged me … and after some google-ing I found that there is indeed such WordPress specific memory limit set in the wp-includes/default-constants.php file …
// set memory limits
if ( !defined('WP_MEMORY_LIMIT') ) {
if( is_multisite() ) {
define('WP_MEMORY_LIMIT', '64M');
} else {
define('WP_MEMORY_LIMIT', '40M');
}
}
if ( ! defined( 'WP_MAX_MEMORY_LIMIT' ) ) {
define( 'WP_MAX_MEMORY_LIMIT', '256M' );
}
So please try and set:
define(‘WP_MEMORY_LIMIT’, ’64M’);
in the wp-config.php file and then retest …
dwinden
I’m confused because the “Allowed memory size of 41943040 bytes” part of the error message would suggest that it is a frontend error (so not a WP Dashboard backend error which up till now I thought it was).
There are 2 memory limit constants in WordPress:
WP_MEMORY_LIMIT which affects the frontend.
If the default PHP memory_limit < 40 MB WP will set the frontend PHP memory_limit to 40 MB unless WP_MEMORY_LIMIT constant is set to a value > 40 MB. WordPress will then set the frontend PHP memory_limit to the value as specified by the WP_MEMORY_LIMIT constant (as long as it is > the default PHP memory_limit).
WP_MAX_MEMORY_LIMIT which affects the backend (WP Dashboard).
dwinden
