Same Old Fatal Error: Allowed Memory Size Problem

[Dokuchie Rob]

There’s something fundamentally wrong with the way this plugin works. I LOVE it. Almost can’t do without it. But this is not the first website I’ve had memory issues with. The second time in eight working days.

I’m getting: Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 262144 bytes) in /home/XXXXXXXX/public_html/wp-includes/option.php on line 253

I’ve increased memory to 256M with php.ini, tried the WP config option too – nothing works.

I’ve had a total of four sites with this problem and the common denominator is Events Calendar. As it is I can’t even get in and fix a site now with memory issues without deleting the plugin.

It’s CLEAR that it’s taking more than its fair share of memory. Someone help? Stop the memory drain?

[Barry]

I’m sorry to hear you’re facing difficulties.

Using The Events Calendar/Events Calendar PRO certainly will add some extra demands – which is true of almost every sizeable plugin – but most users don’t seem to hit this issue (that’s not to excuse this or suggest we’re not interested – as we definitely are interested in finding out more about this).

It also sounds like, despite your efforts, the actual memory limit is significantly lower than what you’re trying to set it to: perhaps your host has enforced an upper limit here?

Can I ask if there is any pattern to these events – for instance, do they always follow a certain set of operations in the admin environment or are they fairly sporadic in nature? Also, what other plugins are running and do you find this occurs if they are deactivated?

[Dokuchie Rob]

I was able to patch the problem – the php.ini wasn’t filtering down into subfolders because of suPHP so I used the solution in the last post here:
https://forums.cpanel.net/f5/custom-php-ini-doesnt-apply-subdirectories-283181.html

That still doesn’t solve the underlying problem. Isn’t there SOME way to change that? The functionality is top notch – but the fact remains is there is still a lot of memory being eaten up.

I get that other plugins do that too – but one plugin at a time 🙂

[Barry]

I’m sorry we missed your reply. We’re continually working to make things more efficient, in the short term though I don’t realistically think there’s much we can offer you, though.

With that in mind I’ll close this thread – but if we can help with anything else please don’t hesitate to post a new thread.

[Author]

Posts