Contrib.social

DB Update 8103 Exhausted Memory

Open on Drupal.org →
Created on 13 March 2023, over 1 year ago
Updated 16 March 2023, over 1 year ago

I'm encountering the following error trying apply Database update 8103:

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /update.php/start?id=12055&op=do_nojs&op=do
StatusText: OK
ResponseText: 
Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in /app/docroot/core/lib/Drupal/Core/Database/StatementWrapper.php on line 145

This is happening on my production server and my staging server, and I can't seem to find any other error messages related to this error. I will test locally with the production database, and with a fresh install to see if I can replicate the error and get more info about the error.

💬 Support request
Status

Active

Version

3.2

Component

Code

Created by

🇺🇸United States safetypin Memphis, Tennessee

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @safetypin
  • Comment over 1 year ago →
    🇺🇸United States safetypin Memphis, Tennessee

    When I run the database updates locally, the main thing that's different is the amount of memory that's exhausted. When I run it locally, the allowed memory size is:

    Fatal error:  Allowed memory size of 1073741824 bytes exhausted (tried to allocate 4096 bytes) in /var/www/html/docroot/core/lib/Drupal/Core/Database/StatementWrapper.php on line 145
Fatal error:  Allowed memory size of 1073741824 bytes exhausted (tried to allocate 65536 bytes) in /var/www/html/docroot/core/lib/Drupal/Core/ProxyClass/Batch/BatchStorage.php on line 91

    .

    I think this could be related to the size of our broken link table: there are more than 218,721 rows. I think it's probably ok for us to just truncate this table, but I'm guessing this is at least somewhat related to the batch process management system.

  • Comment over 1 year ago →
    🇺🇸United States safetypin Memphis, Tennessee

    I'm not really sure this requires any kind of fix. Testing in a local dev environment, I truncated all the broken_link tables and the database updates applied successfully.

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024