Allowed memory size of x bytes exhausted

  • Resolved crdunst

    (@crdunst)


    1 month, 2 weeks ago

    Hi guys, I don’t want to jump in and give you a bad review without flagging up an issue.

    A client reported they couldn’t access their product listing screen in the dashboard. Upon debugging, it seems there’s a fatal error ‘Allowed memory size of x bytes exhausted’. There’s 512mb assigned at the server level, and the WP WP_MEMORY_LIMIT constant is set higher still.

    Disabled plugins in turn identified your plugin as the culprit I’m afraid. Once disabled, the product listing screen loaded fine, and the dashboard has no lag or memory issues. Re-enabling your plugin re-introduced the error.

    The client has 633 published products, out of 1019 in the DB. The ‘number of items per page’ is only set to the default 20 too, so it’s not like it’s trying to pull in hundreds in one go.

    Hope that helps.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter crdunst

    (@crdunst)

    Just more updates, if that helps you…

    I tried to download v3.3.1 from your repo, but when installed, it seems to think that’s v3.3.0. I tried activating anyway, and it gave a WP feedback message that ‘it can’t be activated as it’d give a fatal error’.

    Instead, I deleted the copy from your repo, and grabbed a copy of the original plugin from our server backup, from before we updated the plugin yesterday. When re-installing this (which was in fact 3.3.0), I tried activating this, but it re-introduced the error we had in the first place, i.e. the products listing screen isn’t loading (and presumably exhausting memory). It was working before we updated most of the plugins on the site yesterday.

    So in summary, your plugin was working. We updated plugins including Woo and your plugin. This started exhausting memory. Rolling back your plugin to the previously working version still didn’t fix the issue.

    I’d therefore best guess that the latest Woo version (that we also updated yesterday), isn’t compatible with your plugin from at least 3.3.0 onwards?

    Best regards.

    • This reply was modified 1 month, 2 weeks ago by crdunst.
    • This reply was modified 1 month, 2 weeks ago by crdunst.
    Plugin Support iodic

    (@iodic)

    Hello and thank you for sharing such a detailed report.

    Could you share the following info to help us troubleshoot the issue further:

    • Your site’s?system status report.
    • Are there?any?other?entries?in your debug log?
    • Under the logs section in WooCommerce, do you see any errors?

    Best,
    Marko

    Plugin Support Marija

    (@marijastuntcoders)

    Hello @crdunst ,

    Just wanted to follow up and check if you are still having issues with the plugin? If so, please share your site’s?system status report.

    Also, are there?any?other?entries?in your debug log, or any errors under the logs section in WooCommerce?

    Kind regards,
    Marija

    Thread Starter crdunst

    (@crdunst)

    Hi guys, we’re using an alternative plugin now and don’t have access to the logs from the time.

    I don’t know if you’ve pushed an update and fixed this, but I’ll close the thread as my query is resolved (using another plugin).

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.