Thanks for reaching out @macbeathdigitalsolutions. While I will check with the team for any potential memory leaks, in the meantime, please share the following:
- Your Site Health information for one of the impacted sites. You can use this form to share privately if preferred.
- On your site, can you confirm you encounter the memory leak notice only when using the Site Kit dashboard, without having encountered the error elsewhere on any of these sites?
- Can you share any PHP error log for any impacted site, from immediately after when you encounter the error? Feel free to share privately using the same form above.
Let me know if you have any questions with the above. Thank you.
While you’re checking the above @macbeathdigitalsolutions, if you can also share details of whether you encounter any browser console errors, or maybe even any invalid XHR responses or network requests from the network tab this may also be of use, ideally from a Chrome browser incognito window. To do so, please see the below steps:
- Update from Site Kit 1.141.0 to the last version once more, but don’t yet visit the Site Kit dashboard.
- Right-click a page and select Inspect. This displays the HTML code for the element you clicked.
- Click on the Console tab to view any console errors.
- Navigate to the Site Kit dashboard after updating to Site Kit 1.142.0 once more, on one of your impacted sites. You can then click on the “Network” tab should any issues arise, to view any invalid XHR responses, which you can share from the same form suggested above, when sharing your Site Health information.
Let me know if you have any questions with the above, and please do share the other information requested above while we investigate this further. Thank you.
I uploaded the site health to that form.
The memory leak error only happens when attempting to view the Google Site Kit dashboard. It does not happen anywhere else in the backend or the frontend.
I have not been able to find any PHP error around the same time of this issue. I will keep testing and looking.
I did exactly what you mention in your second reply and added the screenshots to a shared folder that I sent in the form. There was no XHR responses in dev tools. I also added a screen recording that I made yesterday of this issue to walk through the steps I was taking to replicate the error after login.
As you will see in the site health information, I increased the memory limit quite substantially to see if I could get it to work but nothing appears to solve the issue for me.
Many thanks for sharing the additional information @macbeathdigitalsolutions, very useful indeed. We’ve been able to replicate the same issue on a Cloudways site, and we’re narrowing down the cause. To troubleshoot this further, please share the following:
- Does the same occur if you temporarily disable New Relic is active? You’ll find the steps from your Cloudways account here (screenshot)
- Are all the sites you’re using hosted on the same platform?
Let me know if you have any questions with the above. Thank you.
The issue does not occur after I disable New Relic on my server.
All sites that I have hosted are through Cloudways, yes. I do work for another hosting company who have DigitalOcean servers managed with cPanel and they are not affected though.
Appreciate the update @macbeathdigitalsolutions, many thanks. We’ve identified the cause and we’ll have a fix out for the next plugin release, scheduled for Monday. If you wish, you can keep New Relic deactivated until that time if that’s feasible option for you.
Let me know if you have any questions with the above. We’ll also let you know once the release is out, so you can test if you wish. Thanks again for reporting this and sharing insights. This impacted other users also, so with your help the plugin is more robust with the next release.
Fantastic! Thank you for letting me know. I will keep New Relic deactivated until the new release is published.
Just to let you know that we have a fix out for this with the latest version of Site Kit, released earlier this week. Feel free to test this after enabling New Relic once more. Note that while the overall bug you raised isn’t specifically a Site Kit issue, this latest release will ensure such a conflict no longer occurs with the changes made to this latest version of Site Kit.
Let me know if you have any questions with this. Thank you.
I tested the update out with all 11 websites and it appears to be working as expected now. Thank you very much for looking into this issue!
Glad to hear it @macbeathdigitalsolutions, appreciate the confirmation. With that, I’ll close this support topic. If you run into any further errors or if you have any Site Kit related queries, be sure to get in touch.
If you have a moment free please also consider leaving a review, given you’re a user across multiple sites. We’d love to hear your feedback.
