Docs

[Benjamin B]

I installed a fresh copy of X on https://funnytimes.com/testbed and am now having difficulty with custom sidebars. When I turn on debugging, I get this error on the ‘Manage sidebars’ screen:

Fatal error: Out of memory (allocated 81264640) (tried to allocate 94 bytes) in /home/funnyt/public_html/testbed/wp-includes/wp-db.php on line 1837

…but I have a LOT more memory than that allocated to this wordpress build:

define(‘WP_MEMORY_LIMIT’, ‘256M’);
define(‘WP_MAX_MEMORY_LIMIT’, ‘512M’);
set_time_limit(120);

Any thoughts? I’m happy to create an admin account for you so you have access — I’m really stuck until I can create some custom sidebars.

Thanks in advance.

:Benjamin Barnett

[Joao]

Hi Benjamin ,

I recommend you contacting your hosting provider,

Ask them to improve your memory limit, sometimes even if you add the rule :

define(‘WP_MEMORY_LIMIT’, ‘256M’);
define(‘WP_MAX_MEMORY_LIMIT’, ‘512M’);

If your hosting does not allow it, it doesn’t make much difference.

Let us know how it goes,

Joao

[Benjamin B]

Hi Joao. I’ve already contacted my host, and confirmed that a) 1G of memory is made available to wordpress at the server level (in cPanel PHP settings); and that b) the WordPress memory constants are properly applied:

define( ‘WP_MAX_MEMORY_LIMIT’, ‘1024M’ ); // for back-end scripts
define( ‘WP_MEMORY_LIMIT’, ‘128M’ ); // for front-end scripts

…so if the Sidebars admin screen were respecting those limits, a resulting memory error would happen once the process had gobbled up 1G of memory (1024M). That’s NOT what’s happening tho. The error message on Appearance/Sidebars is:

Fatal error: Out of memory (allocated 81002496) (tried to allocate 84 bytes) in /home/funnyt/public_html/testbed/wp-includes/wp-db.php on line 1837

Look at that number closely — the process is capping at 81Mb. That number is nowhere on my build: not at the LAMP stack layer, not in .htaccess, not in the WP constants. Is there some place in the code of ups-sidebars itself, which X seems to incorporate, which caps the memory allocable to sidebar processing functions?

I’m really at a loss here.

:Benjamin

[Benjamin B]

PLUS … this number changes almost every time I load the Sidebars admin screen. It’s always roughly 81Mb, but right now the number is 81526784, not the 81002496 it was a few minutes ago. It’s deeply weird behavior.

:Benjamin

[Darshana]

Hi there,

Would you mind providing us with login credentials so we can take a closer look? To do this, you can make a post with the following info:

– Link to your site
– WordPress Admin username / password
– FTP credentials

Don’t forget to select Set as private reply. This ensures your information is only visible to our staff.

[Benjamin B]

This reply has been marked as private.

[Benjamin B]

This reply has been marked as private.

[Rupok]

Hi there,

Sorry to hear that you are still acing trouble with this. One of our user face the same issue if you see this thread – https://community.theme.co/forums/topic/fatal-error-out-of-memory-allocated-40370176-tried-to-allocate-32-bytes-2/

Finally he figured out that it was a plugin conflict. He suspected iThemes security plugin and I can see you also have this. Although you deactivated this but such plugin saves it’s settings in config file and .htaccess which might be still there and causing issue. You can entirely remove the plugins with all data and check again.

Also you are using PHP 5.5 as I can see on WooCommerce System Status – http://prntscr.com/cq73qy
You should use PHP 5.6+.

Let us know what you find.

[Benjamin B]

So, I deactivated all non-essential plugins, deleted iThemes outright (along with a few others), and left ONLY Cornerstone plugin running. Same error.

I also should note that this sidebar functionality runs fine on another — quite finicky, it’s a multisite that runs iThemes security — build on this same server. I don’t think it’s a PHP 5.5 error, but I just bumped up to 5.6 too.

Out of memory error still persists. Other ideas?

[Benjamin B]

Oh, and I also stripped out everything but the WP core code from .htaccess, but put the extra security stuff back (NOT iThemes-related, other general hardening) when I tested and still got the OOM error on Sidebars management screen. Just sayin.

:B

[Lely]

Hi Benajamin,

Did you figure this out already? There’s no more FATAL error when I checked. See this:http://screencast-o-matic.com/watch/cD6h3ljv21

For section shortcode, is this coming from a plugin? This is because what is available in X is this:
[x_section][/x_section]
There’s is no title option for section shortcode.

Hope this helps.

[Benjamin B]

Hi Lely. The fatal error happens in the back end, not the front end. The error happens on X’s Custom Sidebars management screen, here:

https://funnytimes.com/testbed/wp-admin/themes.php?page=ups_sidebars

Yes, it is totally still erroring.

:Benjamin

[Benjamin B]

Again, just to iterate, I have another, more finicky (multisite, and iThemes Security-running) WordPress build on this server that runs X, and custom Sidebars, just fine.

(http://lightcraftsolutions.com, for reference, although you won’t need to log in because the Sidebars management screen works as expected there.)

[Darshana]

This reply has been marked as private.

[Author]

Posts