Fatal Error, allowed memory size exhausted

  • thomasbadstuebner

    (@thomasbadstuebner)


    8 years ago

    Dear Support Team
    I’m using Participants Database to keep a record information on all the divers who have been diving with my dive centre. I’ve also imported record information from a data set that was exported from Filemaker Pro software.

    This was a CSV import and it works just fine until the number of records tries to exceed 1772. Thereafter I get the following error message any time I try to upload more records or I try to add even a single new record via the Signup page (my site uses a custom template for this).

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 28672 bytes) in C:\xampp\htdocs\signup\wp-content\plugins\participants-database\participants-database.php on line 2071

    If I upload a new record from the “Add Participant” page in the dashboard, it works fine.

    Could you please point me in the right direction as to how I can solve this issue or where the problem might lie?

    Thanks
    Tom

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author xnau webdesign

    (@xnau)

    Are you using the latest version of the plugin?

    Thread Starter thomasbadstuebner

    (@thomasbadstuebner)

    I’m using Version 1.7.0.13
    This appears to be the latest version.

    Plugin Author xnau webdesign

    (@xnau)

    OK, well, this kind of thing is difficult to diagnose because there are so many possibilities.

    What happens when you try to upload your CSV? Do you get the error at that time, or does it happen after you’ve uploaded it and try to upload more?

    Another possibility: take a look at your CSV, make sure there isn’t a syntax error in the file that is causing the CSV to be incorrectly parsed at record 1772.

    Thread Starter thomasbadstuebner

    (@thomasbadstuebner)

    I only get the error message at the time of the upload and thereafter if I try to create a new record via my Signup page.

    I’ve tried these two things today:

    – I got rid of any field data that might contain syntax errors keeping only the straightforward Yes/No data

    – I divided the data set into 3 separate csv files and uploaded them one after the other in a variety of different orders to see whether a single record could be corrupted.

    However the outcome is always the same, as soon as the number of records exceeds 1770 the system reports the same fatal error.

    That’s all I can tell you really.

    Thread Starter thomasbadstuebner

    (@thomasbadstuebner)

    OK, last shot at gaining some insight into this issue.

    I still had a doubt that my import data might be the cause so, to rule out this possibility, I have done the following:

    – deleted all fields and field groups from PD that the plugin will allow me to delete.
    – created a new field called room_number
    – added 20 records manually via the back-end
    – exported the list as CSV via the plugin
    – re-imported the CSV file to check if import works. The import is successful with no errors reported.
    – repeat the export/import process

    The outcome is always the same. Each successive import is successful until 1770 imported records are exceeded. Thereafter the system reports the same fatal error:

    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 28672 bytes) in C:\xampp\htdocs\signup\wp-content\plugins\participants-database\participants-database.php on line 2087

    I am running the latest version of wordpress and the latest version of the PD plugin.
    Imports are set to create a new record with each import as this would be a requirement of the system I’m trying to implement.

    Referring to line 2087 of participants-database.php it seems to me that the problem lies with generating an unique private ID for each new record.
    It’s interesting that this problem only exists when the number of saved records exceeds 1770 and more specifically that it only affects imports via CSV.
    If I add a new record via the back-end then it works just fine. In this case a new record with unique ID is generated almost instantly. However if I try to import even a single new record via CSV then the process terminates in a fatal error.

    Do you think that this issue can be resolved somehow?

    Best regards
    Tom

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Fatal Error, allowed memory size exhausted’ is closed to new replies.