-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drush commands within webroot loop infinitely running out of memory #2755
Comments
drush status in home directory for PHP 7.1.0 info:
|
Does this comment apply here because I installed with
|
Yes it does. |
Thank you for the reply, @weitzman. And I see the note in the master branch version of the documentation now. I think that is prominent enough on the documentation sub-site. I think I'll need to live without drush for core development work flow for now. |
I am just playing with same problem. I have drush launcher of any version(i tried current 0.5.0 too). I have composer based D8 project, drupal is in "docroot" directory. I have there Drush 9.0.0-rc1. So what can cause the problem? Running php7.0-fpm. |
So my temporary solution...
Not the best, i have to type password sometimes but it simply works. Another note: Drupal console + launcher works well without any hacking. This seems to me like regular issue but i am not able to re-open it. |
I am having the same issue.
Noticed that if you have your Drupal installation or parent directory somehow symlinked then this error can occur:
I am assuming drush_locate_root does not work with symlinks. |
Yeah that is the reason for me too. When i am at /var/www/site it works. When i am at ~/www/site (symlink to /var/www/) it fails. |
I think this could potentially be a bug with drupal-finder. |
But Drupal Console uses it too and works without this bug. |
I do not use composer.json in drupal root. I use composer install paths (docroot/core for drupal/core package). I have drupal in subdirectory(docroot) like Lightning and many others have. |
yup I am still not sure ... what's going on. I thought it was related but I don't think it's relevant. |
I am setting up my Drupal 8 vm for 8.4.x core and contrib development and am trying to update and use drush 9 as it is required for Drupal 8.4.x.
composer global remove drush/drush
rm -rf ~/.drush
composer global require drush/drush:^9.0.0-beta1
installed dev-masterf46fe29
, which is the latest commit on master as of 2017.05.13.drush status
in my home directory prints out basic PHP information.drush status
in a Drupal 8.4.x webroot (e67f64e from a week ago) causes drush to loop infinitely trying to fork processesThe following line is repeated until OOM error occurs:
If I remove drush and use
composer require drush/drush:dev-master#990a4b321a1b299c63a1e1eb7b26fdaf0e8c4a50
then the error no longer occurs. So I think this is something to do with PR #2749 which introduced webflo/drupal-finder. I am not sure why it would have issues with the directory that I have checked out as I am using a standard git clone of drupal 8.4.x with a healthy amount of contrib. modules in modules/ that are there for porting/development work. webroot contains the following:OOM error:
The text was updated successfully, but these errors were encountered: