Fatal Memory Error on Schema Aggregation Endpoint

Resolved Roman
(@roman17trushanov)

2 months, 3 weeks ago
Hello Yoast Support Team,

We are encountering a PHP memory exhaustion issue with the Yoast “Schema aggregation endpoint” feature.

When accessing the /wp-json/yoast/v1/schema-aggregator/get-xml/ file, the first URL listed in the discovery XML map throws a fatal out-of-memory error.

Currently, the endpoint generates 2 URLs for our domain. Interestingly, the first page crashes while the second page loads perfectly valid schema.

Failing URL (Page 1): https://www.bussgeld-info.de/wp-json/yoast/v1/schema-aggregator/get-schema/page

Working URL (Page 2): https://www.bussgeld-info.de/wp-json/yoast/v1/schema-aggregator/get-schema/page/2

Error Log:

PHP
```
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 15728672 bytes) in /var/www/vhosts/bussgeld-info.de/httpdocs/bussgeld-info.de/wp-includes/class-wpdb.php on line 1763
```
Questions:
1. Are you aware of this memory limitation regarding the schema aggregator on larger sites?
2. Is there any viable workaround to resolve this?
Thank you for your assistance!

The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)

Plugin Support Jose Varghese
(@josevarghese)

2 months, 3 weeks ago

Hi @roman17trushanov

Thanks for reporting this to us. From the error log, it seems like the error occured as php memory limit set on your website is low for the schema to get processed. Can you please let us know the memory limit you have set for your website, and try increasing it to 2X to see if that helps fix the issue?

We look forward to hearing from you and are happy to help you.

Thread Starter Roman
(@roman17trushanov)

2 months, 2 weeks ago

Thank you for getting back to me!

I increased the php memory limit from 128MB to 512MB. The first page is not failing anymore, although it takes time to load in the browser.

Is there maybe any way to increase the number of pages linked in the graph to distribute the schema more evenly so that the loading time of the single /schema-aggregator/get-schema/page/ is not so slow? or are there any alternative strategies you are aware of?

Thread Starter Roman
(@roman17trushanov)

2 months, 2 weeks ago

On at least one wp-installation the largest file in the xml map, namely

/wp-json/yoast/v1/schema-aggregator/get-schema/page

throws a 504 server-timeout error even after I have increased the php-memory limit to 1024 megabytes.

It´s a cool feature, but its payload should be balanced better from what I have acknowledged during our testings.

Is your team already aware of this issue?

Plugin Support Maybellyne
(@maybellyne)

2 months, 1 week ago

Thank you for bringing this issue to our attention, @roman17trushanov. I’m sorry that our plugin caused a problem on your site. A bug report has been created and is under review by our product team.

What’s next?
Our product team will assess the severity of the issue and assign a priority level to the report. Our developers work on the highest priority issues first. We cannot give you an estimate of when they’ll start working on the issue.

If you have any further information that may affect the prioritisation or help our development team solve this bug, please leave a comment or subscribe to the GitHub report to get updates on the issue: https://github.com/Yoast/wordpress-seo/issues/23076

Thread Starter Roman
(@roman17trushanov)

2 months ago

When I click on the second link you provided me, “This issue has been moved to a repository you don’t have access to.”

Could you please give me an update?

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.