• Subject: Critical Memory Usage and SQL Redundancy Issue with Tablesome Plugin

    Message:
    Hello Tablesome Support Team,

    I would like to request your assistance regarding a serious issue affecting the Tablesome plugin.

    Error Message:
    When deleting or modifying data and then clicking “Update,” the following error occurs:
    SyntaxError: Unexpected token '<', "
    This causes the backend update feature to become unusable.

    In addition, I have identified a more severe problem related to memory usage.
    When updating records in the admin dashboard, the plugin loads all 19,000+ rows into memory at once.
    This behavior leads to Out of Memory (OOM) errors and 502 Bad Gateway crashes.

    Details:
    When memory usage reaches around 7GB, the server’s OOM Killer terminates the Apache process,
    even though the actual table size is only about 5MB.
    This happens every time an update operation is performed, even for small edits.
    It appears that the plugin does not use pagination or batch-loading when processing updates.

    Additional Log Findings:
    From the latest error logs, it seems that the plugin repeatedly calls the
    convert_conditions_to_sql_string() function for the same condition
    (author_id = current_user_id()), generating redundant SQL operations
    and significantly increasing memory usage.

    Request:
    Could you please review whether it’s possible to implement pagination, query caching,
    or other optimization methods during backend filtering or shortcode rendering
    to prevent redundant SQL calls and excessive memory loading?

    Thank you very much for your time and assistance.

    Best regards
    • This topic was modified 7 months, 1 week ago by Tommy.

The topic ‘Request for Assistance – Serious Plugin Error and Performance Issue’ is closed to new replies.