Closed rfay closed 3 years ago
Could you try this with version https://github.com/drush-ops/drush-launcher/releases/tag/0.7.4?
This may be a drush 8.4.5 issue, trying to make a way to repro it.
Although it happens always in CI on quicksprint https://github.com/drud/quicksprint/pull/183 I'm having a hard time making it happen manually (even ssh-ing into circleci).
I thought that we were still composer-installing drush in quicksprint, but I guess the 8.4.x support for D9 let us remove that. So we're actually using drush launcher with drush 8 to do this drush si.
I have some answers.
drush si
just fine with no issues, so that's what I committed to fix this problem. See code# drupal/drupal: This package is meant for core development,
# and not intended to be used for production sites.
# See: https://www.drupal.org/node/3082474
#
# Running 'drush si' to install drupal....
#
# mmap() failed: [12] Cannot allocate memory
#
# mmap() failed: [12] Cannot allocate memory
#
# mmap() failed: [12] Cannot allocate memory
# PHP Fatal error: Out of memory (allocated 4297068544) (tried to allocate 8589934600 bytes) in phar:///usr/local/bin/drush/.box/src/Printer.php on line 61
#
# Fatal error: Out of memory (allocated 4297068544) (tried to allocate 8589934600 bytes) in phar:///usr/local/bin/drush/.box/src/Printer.php on line 61
# Failed to execute command drush si --yes standard --account-pass=admin --db-url=mysql://db:db@db/db --site-name='Drupal Contribution Time': exit status 255
Updated results in https://github.com/drud/quicksprint/pull/188#issuecomment-728035488 using drush si -vvv
I stumbled onto the same memory issue with 0.8.0, rollback to 0.7.4 resolved it
Found the bug. See https://github.com/box-project/box/issues/512
@rfay @csandanov fixed in https://github.com/drush-ops/drush-launcher/releases/tag/0.9.0
Thanks for the bug reports!
Glad you got it fixed, congratulations.
On Drupal 9.1.x, using drush launcher to run site-installed drush:
Why is drush launcher trying to use all that memory in Printer.php?
I think I can work around this in quicksprint by just running vendor/bin/drush, but had hoped not to see this kind of behavior change.