HUGE Memory Problems

The errors are registered in error_log of WordPress site file in the root.

Some of them point to the plugin, others point to WP files but definitely are because of the plugin.

__

[17-May-2016 19:06:03 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /home/wp-content/plugins/autodescription/inc/classes/query.class.php on line 98

__
[17-May-2016 23:55:18 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /home/wp-includes/query.php on line 45

[18-May-2016 06:55:45 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /home/wp-includes/wp-db.php on line 1209

[18-May-2016 06:56:23 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /home/wp-includes/class-wp-term.php on line 206

[18-May-2016 04:39:54 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /home/wp-includes/formatting.php on line 1579

Hi MassimoD,

I believe this is caused by a memory leak, either in The SEO Framework (which I extensively debugged using Xdebug) or in another plugin or theme.

Using up 256MB shouldn’t happen, it should be at most ~96MB for a rather heavy website.

You can confirm a memory leak with a specific plugin or theme using this plugin and disabling others one by one. Keep an eye out for the “MB” usage in the WordPress admin bar.

If disabling The SEO Framework leads you to use less than ~96MB, I believe this leak is within The SEO Framework. Although the errors you get seem to be related to The SEO Framework as it hooks into many places, just like WordPress is outputting these messages as it’s hooked everywhere.
But we can’t exclude The SEO Framework to be the issue just yet.

I’d also like to know if this is happening on all pages, or just some specific ones. That would really help a lot :).

Thank you so much for your time! And I hope we can resolve this together :).

Sorry, i can’t do that kind of debug. One by one. Impossible for me.

My 3 websites were working just fine for years. I reverted back to your previous version and now i’,m ok.

I understand MassimoD,

It’s very hard to control WordPress’ Open Source’s nature as anyone can make adjustments to it and a lot is out of the scope of the developers. So sometimes “one-by-one” is the only resolution pinpointing issues at some point. Nevertheless, I understand that it’s a big hassle.

Just out of curiosity, what’s the total memory usage with the previous version active? I’m also still unsure if this issue is bound to a specific page (type) or the whole website.
That information might describe that the cause of the error lies within the new version and might help a lot of users as well :).

I’ll be sure to keep you notified on this topic when any progression regarding this subject has arisen.

Thanks and have a great day!

Not sure how you see the memory used. From a plugin i use, it says:

Peak memory usage 12 MB (home page) and 15 at my admin dashboard.

I can verify that after several hours to the pre 2.6 version, my error_log is empty.

Thanks

Here is an other one during my tests for the sitemap plugin:

[18-May-2016 14:54:24 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /home/wp-content/plugins/autodescription/inc/classes/query.class.php on line 122

Hi MassimoD,

Do you remember on which page that was?
Was it within the admin, the sitemap, on a product, archive, etc.?

Thanks!

The errors are appearing in the error_log, i can’t tell where it happens.

No problem!
It’ll make finding a bit harder, but I’ll do my best!

I’ll keep you updated once I know more. Thanks for all the information! ??

Ok, i did install a dev system (with 128 mb allowence) and trying to help.

When i click to a tag, i get:

[18-May-2016 16:22:09 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in /home/p-includes/wp-db.php on line 1264

Disabling your plugin, works just great.

Let’ s see what else i can find …

You’re awesome MassimoD! Keep them coming! ??

Hi MassimoD,

I did some “logical” testing, and I found that there was an infinite loop when the ID couldn’t be defined at a very early stage. This caused the memory to heap up.

If you’d wish to test a beta of the upcoming version and confirm that the notice is gone, I can then with pride upload version 2.6.1 in moments after :).

Let me know! ??

With todays update, i have the EXACT same problems.

Pitty, since that was a nice plugin.

This thread is continued here.

Therefore this one is marked as resolved.