-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Memory limit #3208
Comments
Composer does not have a 512M memory limit. |
Sorry for wording it that way, I understand it isn't a "limit", as it only sets it to that value if the limit is already below than that. Coming from a clean OSX install ( |
Ok, so running composer on your project uses more than 512MB of memory. |
{
"require": {
"laravel/framework": "4.2.*",
"internal/administrator": "*@dev",
"rhumsaa/uuid": "~2.7"
},
"require-dev": {
"barryvdh/laravel-ide-helper": "1.*",
"way/generators": "2.*",
"fzaninotto/faker": "~1.4"
}
}
{
"require": {
"barryvdh/laravel-ide-helper": "1.*",
"imagine/imagine": "~0.5.0",
"anahkiasen/html-object": "~1.4",
"anahkiasen/underscore-php": "~1.2"
}
} The memory limit is hit with the following error:
|
With
|
That particular repository is only a master branch without any tags/releases. Perhaps that has something to do with it? |
IIRC, composer only scans the latest commit on every branch & tag, so that should not be a problem. I have already used VCS repositories with only a master branch without any trouble. |
to make sure to not hit the php memory limit, set another one with "php -d" and to make sure to get no timeouts you can also add: "COMPOSER_PROCESS_TIMEOUT=60000", sometimes I needed it in case of timeouts example:
|
limit is now 1GB and we have improved on memory usage quite a bit so closing |
Recently I've been consistently hitting composer's 512M limit, so I've created a wrapper
composer-infmem
that I can use instead.For slightly bigger projects is it common to consistently hit the limit (on updates/requires)? Is it time to consider lifting the limit from 512M?
(Also worth tagging homebrew/homebrew-php#1210)
The text was updated successfully, but these errors were encountered: