Allowed memory size of 268435456 bytes exhausted (tried to allocate 81920 bytes)

  • Resolved Michael

    (@cajebo)


    3 months ago

    Greetings from SW Ohio.

    We’re experiencing an issue with regard to being able to successfully download submissions.
    (We also have GravityExport installed.)
    Since this was reported this morning, the steps I’ve taken so far is to allocate additional memory via php-ini, with the PHP: memory_limit now set to 1024M
    Still no luck. Any assistance would be greatly appreciated.

    GravityExport Lite: Something is broken

    Error message:Allowed memory size of 268435456 bytes exhausted (tried to allocate 81920 bytes)

    Include the following details in your message:

    • Plugin Version: 2.3.5
    • Gravity Forms Version: 2.9.0
    • PHP Version: 7.4.33
    • WordPress Version: 6.7.1
    • Error message: Allowed memory size of 268435456 bytes exhausted (tried to allocate 81920 bytes)

    Error stack trace:

    #0 [internal function]: GFExcel\Renderer\AbstractPHPExcelRenderer->fatalHandler()
    #1 {main}

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Doeke Norg

    (@doekenorg)

    Hi @cajebo!

    If the error remains the same, then something is still not set correctly for the memory limit. The amount of 268435456 bytes comes down to 256MB. Which means that the increase to 1024 did not take.

    Please have a look at this page as it might help. https://woocommerce.com/document/increasing-the-wordpress-memory-limit/

    Hope this helps you out.

    Kind regards,

    Doeke

    Thread Starter Michael

    (@cajebo)

    Doeke, I bow in your presence.

    Reason: to assuage you when I admit that regenerating the URL has resolved the issue. Odd in that we’ve made no revisions to the form in more than a year. My thought is that the update to GravityKit and/or GravityExport might have been the cause.
    Even so, I’m grateful for your being here and the fast action of your reply.

    Have you a buy-me-a-coffee/beer/whiskey link you’d like to share? ??

    Cheers from Southwest Ohio,

    –Michael

    Thread Starter Michael

    (@cajebo)

    Follow up–

    W/regard to “Which means that the increase to 1024 did not take”, I think it actually did. Divi theme has a support page that when refreshed after a php-ini revision, it shows what the values changed to, and this site’s support center tab shows as much. That does NOT lessen my appreciation of your looking this over in any way,

    • This reply was modified 3 months ago by Michael.
    Plugin Author Doeke Norg

    (@doekenorg)

    Hi @cajebo. No need to bow!

    The increase in memory usage comes with every new entry that is added. So while you didn’t change your form, the entries contribute to the memory usage. This is because the XLSX needs to be written as a whole, because XLSX (and DOCX for that matter) are actually a zip file of a bunch of XML files. So where a CSV could just append a row to a file, a XLSX must be generated in memory completely, before it is written to the file.

    Sorry for nerding out.

    There is no need for the coffee. But I thank you for your kind gesture.

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