[Support request] Fatal Error – GP Memory Leak/Utilising Large Amounts of Memory

[Colin]

Hi,

We are not technical. After spending some time with our host, Kinsta on a fatal memory issue.

They have pointed us in the direction of GP to seek some guidance on what the problem could be. “Looks like 256M could simply be insufficient for this theme. Would it be possible to contact the developers and check if there are any specific requirements for the memory and if it’s possible to run the theme on 256M?”

We experience a fatal error more often when we are in the WP backend, editing theme options. Appearance > GP > Start Customising (blue open options) = Fatal Error – This happens more often when Woocommerce is active.

Any ideas on what we can do to fix this?

[David]

Hi there,

so this: Appearance > GP > Start Customising (blue open options) are simply shortcuts to the various Customizer panels.
What happens if you go direct ie. Appearance > Customizer ?

[Colin]

Hi David
Sure, if we go direct ie Appearance > Customiser, the following:

There has been a critical error on this website. Please check your site admin email inbox for instructions.
Learn more about troubleshooting WordPress.

[Colin]

Worth noting, PHP memory limit is set to 256.

[David]

ITs super unlikely that the Theme is directly responsible for the error. We host on Kinsta and probably use the same memory limits you are. We may not run Woo on here but we do run other memory intensive plugins.

Is it possible to get an error log ? It would be good to see the stack trace so we can help you debug the issue ?

[Colin]

Sure no problem, here is a snapshot:

2022/09/06 08:39:40 [error] 22638#22638: *110264 FastCGI sent in stderr: “PHP message: PHP Deprecated: Return type of MyCLabs\Enum\Enum::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/airacom_469/public/wp-content/plugins/woocommerce-payments/vendor/myclabs/php-enum/src/Enum.php on line 246” while reading response header from upstream, client: 82.16.124.23, server: staging-airacom.kinsta.cloud, request: “POST /?wc-ajax=get_refreshed_fragments HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php8.1-fpm-airacom.sock:”, host: “staging-airacom.kinsta.cloud:56460”, referrer: “https://staging-airacom.kinsta.cloud/industries/transport-and-logistics/automotive/”
2022/09/06 08:39:40 [error] 22638#22638: *110259 FastCGI sent in stderr: “PHP message: PHP Deprecated: strstr(): Passing null to parameter #1 ($haystack) of type string is deprecated in /www/airacom_469/public/wp-content/plugins/woocommerce/includes/wc-page-functions.php on line 139” while reading upstream, client: 82.16.124.23, server: staging-airacom.kinsta.cloud, request: “GET /industries/transport-and-logistics/automotive/ HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php8.1-fpm-airacom.sock:”, host: “staging-airacom.kinsta.cloud:56460”, referrer: “https://staging-airacom.kinsta.cloud/”
2022/09/06 08:39:40 [error] 22638#22638: *110259 FastCGI sent in stderr: “ecated in /www/airacom_469/public/wp-includes/functions.wp-styles.php on line 90” while reading upstream, client: 82.16.124.23, server: staging-airacom.kinsta.cloud, request: “GET /industries/transport-and-logistics/automotive/ HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php8.1-fpm-airacom.sock:”, host: “staging-airacom.kinsta.cloud:56460”, referrer: “https://staging-airacom.kinsta.cloud/”
2022/09/06 08:39:40 [error] 22638#22638: *110259 FastCGI sent in stderr: “PHP message: PHP Deprecated: stripos(): Passing null to parameter #1 ($haystack) of type string is depr” while reading upstream, client: 82.16.124.23, server: staging-airacom.kinsta.cloud, request: “GET /industries/transport-and-logistics/automotive/ HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php8.1-fpm-airacom.sock:”, host: “staging-airacom.kinsta.cloud:56460”, referrer: “https://staging-airacom.kinsta.cloud/”
2022/09/06 08:39:40 [error] 22638#22638: *110259 FastCGI sent in stderr: “PHP message: PHP Deprecated: Return type of MyCLabs\Enum\Enum::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/airacom_469/public/wp-content/plugins/woocommerce-payments/vendor/myclabs/php-enum/src/Enum.php on line 246PHP message: PHP Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/airacom_469/public/wp-includes/Requests/Cookie/Jar.php on line 63PHP message: PHP Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/airacom_469/public/wp-includes/Requests/Cookie/Jar.php on line 73PHP message: PHP Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/airacom_469/public/wp-includes/Requests/Cookie/Jar.php on line 89PHP message: PHP Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/airacom_469/public/wp-includes/Requests/Cookie/Jar.php on line 102PHP message: PHP Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /www/airacom_469/publi

[David]

Do you know what PHP version is running on the site ?

[Colin]

Currently 8.1, however, we have tried running 8.0 and 7.4.

[David]

Is it possible to get an admin login to the site so i can take a closer look ?
You can provide any login details in the Private Information field.

[Colin]

Sure I will add it to the private information area

[Colin]

Information provided in the private information area

[David]

Can you confirm the login as those are not working for me?

As a general note – i see a lot of deprecation notices on the front end of the site. Are they present when using PHP 7.4 ?

[Colin]

Understood. We have reset the credentials, new are below in the private information area.

Front end site, do you mean the staging site? – If yes, not sure if this makes a difference but we have Kinsta APN running and debugging enabled.

Or do you mean the actual live domain (not staging) – If yes, not aware. This site was migrated from AWS and will be replaced with the staging site swiftly.

[David]

Front end site, do you mean the staging site?

Thats correct.

I had a look around, couldn’t see anything that stands out as an issue.

What happens if you temporarily switch to a Twenty something theme ?

[Colin]

Switched to a Twenty-something theme. Deactivated all GP plugins.

Different areas of the WP backend selected load fine. Replicating the fatal error seems to be when you select Appearance > Customise or Appearance > Background

Both deliver the following:
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 192512 bytes) in /www/airacom_469/public/wp-includes/wp-db.php on line 2141
There has been a critical error on this website. Please check your site admin email inbox for instructions.

[Author]

Posts