• Resolved mtg169

    (@mtg169)


    We are seeing numerous sites suffer from various memory exhaustion fatals since auto-updating to 7.2.0. These are a couple of examples:

    Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /srv/htdocs/wp-content/plugins/wp-retina-2x/classes/core.php on line 1457

    Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /srv/htdocs/wp-content/plugins/wp-retina-2x/classes/core.php on line 2435
Viewing 4 replies - 1 through 4 (of 4 total)
  • justin-bigscoots

    (@justin-bigscoots)

    Seeing the same across many sites, can’t even roll the plugin back unless you skip it:

    # wp plugin install wp-retina-2x --version=7.1.9 --force
    Segmentation fault


    # wp plugin install wp-retina-2x --version=7.1.9 --force --skip-plugins=wp-retina-2x
    Installing Perfect Images: Regenerate Thumbnails, Image Sizes, WebP & AVIF (7.1.9)
    Downloading installation package from https://downloads.wordpress.org/plugin/wp-retina-2x.7.1.9.zip...
    Unpacking the package...
    Installing the plugin...
    Removing the old version of the plugin...
    Plugin updated successfully.
    Success: Installed 1 of 1 plugins.

    Also seeing the same. I discovered the issue only after it completely borked a SimplyStatic export. I wonder who’s to blame, Fable or GPT. @justin-bigscoots you are the man with that wp fix. 👍🏼

    This error started coming here too:
    [05-Sep-2026 02:48:48 UTC] PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes) in /home/nopubco/public_html/wp-content/plugins/wp-retina-2x/classes/core.php on line 1457

    Plugin Author Jordy Meow

    (@tigroumeow)

    Hi @mtg169, @codyjoyce80, @jamesjosephfinn, @justin-bigscoots 😅

    Sorry about this! It is a real bug in 7.2.0. When the plugin decides its settings need a small cleanup, the routine that saves the settings and the routine that reads them ended up calling each other, with nothing to stop the loop…

    Version 7.2.1 is out with the fix.

    For anyone still stuck, the workaround Justin posted above is the right one. The plugin has to be skipped during the rollback, otherwise it loads and takes the command down with it. Renaming the plugin folder over FTP works too, then update normally from the dashboard.

    @jamesjosephfinn, your SimplyStatic export failed because the pages themselves fataled halfway through, so a fresh export after updating should come out clean.

    Thanks again for reporting this so quickly, and sorry for the trouble it caused 🥲 Have a nice week-end ahead ☀️

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

You must be logged in to reply to this topic.