Composer running out of memory on every project, Mac OS X

Question

I attempted to install aws/aws-sdk-php yesterday on one of my Laravel 4 projects using Composer, I cannot remember exactly the chain of events but it did not in

Answer 1

try this. It fixed my problem.I guess better way to fix it rather than update memory.

sudo composer self-update

Answer 2

Easiest way to fix this on Windows is:

Goto: C:\ProgramData\ComposerSetup\bin

Edit composer.bat

Change it to:

@ECHO OFF
php -d memory_limit=-1 "%~dp0composer.phar" %*

Save the file and run:

composer selfupdate

Answer 3

EDIT: Before going any further always make sure you're running the latest version of composer, you can update it via composer self-update

When you run composer update it will calculate the most up-to-date gitref for each of your libraries (or the latest release) and then will install that version of the library. It will then store these versions in the composer.lock file.

When you run composer install, it simply installs the versions defined in the composer.lock file.

The reason composer update takes so long and uses so much memory is because it has to trace every library's version, compare it with the version you have defined in your composer.json and then check all of that library's dependencies. This is quite an intensive process.

I find that running composer using hhvm (you can install it here) speeds up the composer update process massively.

Short of that, you just have to live with the high memory usage and increase it in your php.ini file. Make sure you update the one that is relevant for your CLI.

EDIT: You should never run composer update in the production environment. You should only update your dependencies when you're developing, and then use composer install to install your last used set of composer dependencies when you're in a production environment.

Answer 4

At the present moment there is a bug on Composer causing memory to be exhausted.

If you do

composer install

Then delete a folder inside vendor

rm -rf vendor/laravel

and do

composer update

You'll get this error. It's a bug, it is not supposed to run out of memory.

For now you can fix it for yourself by doing:

php -d memory_limit=-1 /usr/local/bin/composer update

Also, check this thread, they are about to fix this.

Answer 5

do not do any thing only try this code if your version is 1.*:

 composer self-update --2   

i was facing many problem then i given memory_limit : 10G. after that i was getting same issue then i try to update composer version then it gone fix. you can check compser version

 composer --version

Answer 6

The reason why it was taking so much memory is because of the behaviour of Composer when treating packages and the replace keyword.

The idea behind replace was that it allowed you to do two things:

• Replace a standard library version with your own version. e.g. if you find an example in 'symfony/yaml' you could fork it, fix the bug and then release it as a package called "nightmicu/yaml". You could then tell composer that "nightmicu/yaml" replaces "symfony/yaml". Then any other package that you install that depends on "symfony/yaml" will be satisfied by having "nightmicu/yaml".

• It allows people to release packages both as single components, as well as a complete library e.g. the symfony framework package replaces each of its components packages.

The problem is that the replace keyword, up to about 1 hour ago, worked globally across the whole of Packagist.

This means that for popular libraries, that have been forked and renamed there is a huge amount of possible versions to install. This is what was causing a huge memory usage, and taking a long time to process.

If you get the latest version of composer.phar, it should be better now, as 'replace' now works differently, by only working on packages named in the root composer.json i.e. you have to explicitly use a package in your composer.json to have it be either replaceable or act as a replacement, though I haven't been able to test it myself.