Title: database update process
Last modified: December 29, 2025

---

# database update process

 *  [Carlo Buttinoni](https://wordpress.org/support/users/buttinoni/)
 * (@buttinoni)
 * [3 months, 2 weeks ago](https://wordpress.org/support/topic/database-update-process/)
 * Hello, my site [http://www.buttinoni.it](http://www.buttinoni.it) has been giving
   me this error for a few days:
 * “Elementor data update
 * The database update process is running in the background. Is it taking a while?”
 * And if I click to run it, it gives me an error:
 * A critical error has occurred on this site. Check the incoming emails in the 
   site administrator’s mailbox for instructions. If you continue to have problems,
   try the support forums.
 * I also contacted my provider and this is the answer:
 * Thank you for your reply.
 * The exact issue that is showing up after the “Update DB data” in Elementor is
   clicked is:
 *     ```wp-block-code
       Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 229855936 bytes) in /home/buttinon/public_html/wp-includes/class-wpdb.php on line 2357
       ```
   
 * We have noticed such an error before with other clients, and regardless of how
   much we increase the PHP memory, the error message still stays.
 * The way our clients resolved that issue was by contacting the support of Elementor,
   who then looked into the Elementor setup of the site and made configurations,
   so that the error does not show again.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fdatabase-update-process%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 4 replies - 1 through 4 (of 4 total)

 *  [modiphier](https://wordpress.org/support/users/modiphier/)
 * (@modiphier)
 * [3 months, 2 weeks ago](https://wordpress.org/support/topic/database-update-process/#post-18770201)
 * I am getting the same error and now i notice my site is not formatted unless 
   I am logged in as an admin.
 *  Plugin Support [Rica](https://wordpress.org/support/users/ricav/)
 * (@ricav)
 * [2 months, 3 weeks ago](https://wordpress.org/support/topic/database-update-process/#post-18790291)
 * Hi [@buttinoni](https://wordpress.org/support/users/buttinoni/),
   Based on the
   error log you provided, the issue is due to insufficient memory resources. With
   that in mind, please reach out to your hosting provider and as them to increase
   both PHP and WP memory limits of your website.
 * Let us know if you need further assistance, we will be more than happy to help
   you.
 * Best regards,
 *  Thread Starter [Carlo Buttinoni](https://wordpress.org/support/users/buttinoni/)
 * (@buttinoni)
 * [2 months, 1 week ago](https://wordpress.org/support/topic/database-update-process/#post-18810767)
 * Hi,
 * I increased the memory to 1024 but updating the elementor data I find myself 
   with this error:
 * Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate
   4138440 bytes) in /home/buttinon/public_html/wp-includes/functions.php on line
   655
 *  Plugin Support [Milos](https://wordpress.org/support/users/miloss84/)
 * (@miloss84)
 * [1 month, 2 weeks ago](https://wordpress.org/support/topic/database-update-process/#post-18830388)
 * Hi,
 * Thank you for your patience,
 * Even though the memory limit was increased to 1024MB, the error indicates that
   WordPress is still exhausting the available PHP memory during the Elementor data
   update. This usually means that the new memory limit is either not actually being
   applied to the active PHP process, or that the effective server-level memory 
   limit is lower than expected. In some cases, the update process may also be consuming
   unusually high memory due to large amounts of data, a plugin conflict, or a server
   configuration issue.
 * To properly verify this, we recommend checking the active PHP configuration using
   a temporary phpinfo file to confirm the actual memory_limit value in use and 
   identify which php.ini file is loaded. If the limit is lower than 1024M, it should
   be updated in the correct location depending on the server setup.
 * This may involve adjusting the value in wp-config.php using WP_MEMORY_LIMIT and
   WP_MAX_MEMORY_LIMIT, updating the memory_limit directive in a .user.ini file,
   modifying it via .htaccess if the server allows it, or changing it directly from
   the hosting control panel such as cPanel or Plesk. After making changes, it’s
   important to recheck phpinfo to ensure the new limit is applied.
 * If the memory limit is confirmed to be 1024M and the issue persists, the problem
   may be caused by a plugin or theme conflict or an unusually large dataset. In
   that case, temporarily switching to a default theme and deactivating all plugins
   except Elementor can help isolate the issue.
 * Please let us know the current memory_limit value shown in phpinfo, your server
   environment (for example Apache with mod_php or PHP-FPM), and where the memory
   limit was modified so we can provide more precise guidance.
 * Best regards,

Viewing 4 replies - 1 through 4 (of 4 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fdatabase-update-process%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/elementor/assets/icon-256x256.gif?rev=3444228)
 * [Elementor Website Builder - more than just a page builder](https://wordpress.org/plugins/elementor/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/elementor/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/elementor/)
 * [Active Topics](https://wordpress.org/support/plugin/elementor/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/elementor/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/elementor/reviews/)

 * 4 replies
 * 4 participants
 * Last reply from: [Milos](https://wordpress.org/support/users/miloss84/)
 * Last activity: [1 month, 2 weeks ago](https://wordpress.org/support/topic/database-update-process/#post-18830388)
 * Status: not resolved