X + WP 6.2 = critical error (fatal error: memory size exausted)

Support
#1

Hello,

I’m using X that I bought in June of 2022, which I’ve never updated, if that tells you the version. I’m not using a child theme.

My site auto-updated to WP 6.2 last night. Soon as it did, the site broke. Getting the “There has been a critical error on this website,” message when trying to view front end. All pages are affected. Can’t access the dashboard.

Looking at my error log, it’s getting inundated with “fatal error: memory size exhausted” messages, after the WP 6.2 update. For example:

[30-Mar-2023 02:46:16 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 8192 bytes) in /home4/camphik3/public_html/wp-includes/class-wp-dependencies.php on line 260

That example is just the first of hundreds of similar memory exhausted errors.

How do I fix this?

Does adding the return; to line 194 of framework/legacy/functions/plugins/cornerstone.php fix this issue?

Line 194 on notepad++ just looks like a //. Do I just move this and everything below it down a line and paste the return; there?

Line194
Line1941920×1080 350 KB

Or do I ask for higher memory allocation in my wp-config.php file?

Sorry I’m new to all of this, and am not too computer savvy.

Thanks,
Andrew Feazelle

#2

No amount of extra memory will help as you are in an infinite loop.
Yes the return; will help you here and this is the same WordPress 6.2 issue. The notes in stickied post about removing the folder and uploading the new X will help you as well. Let me know if you have any additional questions.

#3

Thanks Charlie - let me try to just do the ‘return;’ method first, as I don’t have access to my dashboard.

I’ve even tried getting to the dashboard via: https://camphikelivecalifornia.com/wp-login.php?action=entered_recovery_mode but couldn’t get in.

But was unable to get in.

#4

Hi @charlie - I’m not sure but is it the case that the file for X and Pro are slightly different? I looked at both and I wonder if it is line #260 in X and not #194

#5

Okay, I tried the return; method, but didn’t have any success.

Just to reiterate what I did, I hit return on line 194, moving // down to 195 (moving everything below it down one line as well), then entered return; on that line.

I then saved my changes and tried to access the front end of my site with no luck.

What’s my next option? Should I rename my X folder to something else and hope that WP defaults to a twenty-twenty-one or similar theme. Then if that occurs, log into dashboard and update to Pro?

Thank you,
Andrew Feazelle

#6

@andrewfez read my note just above here - could try line #260

#7

Okay thanks - I’ll try it!

#8

Hi Spedney,

Thank you!

return; on line #260 fixed the issue on my version of X.

My site is running fine now (back to normal), and I have access to the dashboard once again.

I really appreciate the help!

1 Like
#9

Awesome, okay yes I’ve confirmed that on Pro5 and X9 it is line 260. Thanks a bunch @spedney.

1 Like
#10

Cool. Thanks Charlie! I appreciate you guys!

1 Like
#11

Hi Charlie,

I spoke too soon. Now that my browser’s cache has the latest iteration of my site, I’m seeing the following:

Looks like now I’m having major formatting issues on the X pages and my header drop down menus aren’t dropping down when hovering over them.

Further, Cornerstone page builder won’t load individual pages to work on. When I select a page to work on, it just goes to a grey blank screen of death.

My individual WP blog posts look okay though.

Now that I can access my dashboard, I did notice I am using X 10.1.10, which probably auto updated recently.

Should I manually download a fresh 10.1.10, then reinstall it?

Anyway, I have to go work on taxes, so no rush. You’ve probably got your hands full after this update. I’ll check back later in the day…

See ya,
Andrew Feazelle

#12

Im facing the same problem, I cannot login to system, is there possible to get a link for a recovery mode in my email?

#13

@andrewfez try updating cornerstone too. I noticed that is a version behind.

@Fridriksdottir Yes, but emailing needed to be setup on your server prior to this. See the url in this guide.

#14

Thanks Charlie,

Updating Cornerstone seemed to have fixed all the formatting and menu problems. I haven’t tried page builder, but assume it’s okay since everything else was fixed with the update.

I’ve officially survived WP 6.2

Now just have to survive tax season…

Take care,
Andrew Fez

#15

Hi Andrew,

Glad to know it is fixed now.

Thanks

#16

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.