By bugiboop on

Apologies if this is post is in the wrong area, but I just had an odd thing happen.

I'm running a multi-site Drupal 9 installation on a CentOS distro, and I just updated the core package and modules to 9.3.12. This installation is currently not accessible outside of my network.

I ran the update script that Drupal prompted me to run after updating the modules from within the browser, and was met with the white-screen-of-death. After reading the logs, I saw that I was exceeding the PHP installation's max allocated memory by a LOT... My previous setting was the standard 128M. After the update, it's requiring close to 4GB. I thought it was just for running the script, so I edited the ini to 4G and ran the script on all of the sites. I'll note that the site is incredibly slow when the memory limit is set to 4G. I don't know whether it's because it's using all of that or not. After reverting the ini change back to 128M, I'm met with a WSoD again--the site is still trying to consistently use close to 4G of memory.

Why is this happening, and can it be fixed? It was totally fine prior to the update. According to the logs, it seems to be kint related, but I still have need of kint. I'll post the relevant error log below:

AH01071: Got error 'PHP message: PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 3464645992 bytes) in /{root}/vendor/kint-php/kint/src/Utils.php on line 121'

Thanks for the help!

⋅ Categories: Drupal 9.x

Comments

bugiboop’s picture

bugiboop commented

I figured out the issue. I'm not 100% sure how it happened, but I think due to a malformed tar command, my composer.json was corrupted and was listed to be 3.3GB or so. After restoring a sadly out-of-date backup of that file, and updating it with the required modules, the site is running well and I was able to set the memory limit back down to acceptable limits.