PHP Fatal error  Allowed memory size exhausted from ActionScheduler_Lock.php

  • tomachi

    (@tomachi)


    1 day, 9 hours ago

    Perhaps the solutions proposed at the linked page will resolve my issue (out of memory). I have not tried them but I am about to. I was just intending to dump this log line on the thread but it has been CLOSED for some reason. I reckon 2 years should be a minimum to close a thread on the internet generally. Anyhow. HJere is the log line taking down my site intermittently. It could be my host running out of resource. I mean… it only has 502 GB of RAM… ? Need php.ini? can send…

    [Fri Aug 07 21:51:25 2026] [tomachi.co] [warn] [client 101.98.182.135:37038] [pid 1827009
    ] fcgid_bucket.c(153): mod_fcgid: stderr: PHP Fatal error:  Allowed memory size of 134217
    728 bytes exhausted (tried to allocate 32768 bytes) in /home/tcorp/tomachi.co/wp-content/
    plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler_Lock.php
    on line 1

                  total        used        free      shared  buff/cache   available
    Mem:           502Gi       120Gi       105Gi        11Gi       292Gi       382Gi
    Swap:             0B          0B          0B

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    1 day, 4 hours ago

    Hi @tomachi!

    Thank you for sharing the error log and the additional details.

    The error shows that the PHP process is reaching its 128 MB memory limit while Action Scheduler is running:

    Allowed memory size of 134217728 bytes exhausted

    Although your server has 502 GB of RAM available, PHP has its own per-process memory limit, so the amount of total RAM available on the server doesn’t prevent an individual PHP process from reaching that limit.

    The more important question is what is causing the PHP process to consume that much memory. The fact that the error occurs in ActionScheduler_Lock.php does not necessarily mean Action Scheduler itself is the cause; it may simply be where PHP ran out of memory while processing a scheduled action.

    Could you please share your WooCommerce → Status → System Status Report with us? You can paste the report on Pastebin and enable the Burn After Read option before sharing the link.

    Also, please go to WooCommerce → Status → Scheduled Actions and share a screenshot of the Pending and Failed actions. This will help us check whether there are any unusual scheduled actions that could be contributing to the issue.

    With this information, we can investigate further and try to determine what is causing the memory usage to reach the PHP limit.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.