ErrorException: proc_open(): fork failed - Cannot allocate memory in phar #945
Comments
|
In order to resolve this issue I had to make sure there was over 1 gig of memory available. |
|
I was also having this issue but increasing the PHP memory_limit solved the problem. |
|
Same here: More info about the system: php -v
PHP 5.3.10 (cli) (built: Feb 20 2012 16:56:36)
Copyright (c) 1997-2012 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2012 Zend Technologies
with Xdebug v2.2.1, Copyright (c) 2002-2012, by Derick Rethans |
|
Got the same error two times, but can say: It work around an hour ago (without any change on the setup) and now in the third try it works again (without any change at all). Update:OK, forget it. I forgot to enable the swap again... The machine really ran out of memory... |
|
Had the same issue when trying to do a deployment to an Amazon AWS EC2 Micro instance. These instances have only 613MB of memory in total so composer fails to allocate enough memory for an update to run. Upgrading to a Small instance with 1.7GB of total memory got rid of the issue. |
|
I have the same issue .... does composer really need so much memory? :-O |
|
I guess it's not composer itself, but anyway: The micro instances on ec2 doesn't have any swap memory (by default) and so the OS kicks the processes, if it runs out of memory. The better solution instead of upgrading to small (because it costs more) is to create a file based swap (at least temporary) For example. 613M is very less and remember, that not only PHP consumes it. I don't think one can blame composer for it. Can somebody close this issue? |
|
I am running into this issue again. Here is my Dump: Doing a Dry-Run with Profiling returns the following mem usage info: |
|
Hi, Just a guess: Do you running this on a AWS-micro? Do you have a swap Regards, 2012/12/20 Dan Horrigan notifications@github.com
github.com/KingCrunch |
|
@dhorrigan ouch according to the stack trace it looks like the fatal error was triggered while rendering an exception (since that uses proc_open to check for your terminal width). Looks like it's not a php memory limit but rather the machine's memory that ran out, so I would suggest clearing other things, and running it with install instead of update if you can run update somewhere else that has more memory. install from lock file uses very little memory. |
|
I am running this in a Vagrant box, and there is quite a bit running on it, but this is the first time I have seen it. I will try re-building the box with more memory and see what happens. I will follow up. |
|
To be honest 67MB isn't so big. I can see how it's a problem if it fails, but in this day and age a couple hundred megs of peak memory isn't so much to ask for ;) |
|
Ya, found the problem, the VM only has 6MB of mem available (out of 512MB) so, ya. Haha, I am upping it to have 1GB of memory. Should have checked that first. Carry on. |
|
@Seldaek The micro instances have 590MB and by default no swap. For playing around this works fine, but as soon as some application needs a little bit more it completely breaks. So as mentioned earlier: Creating a swap catches this :) It only takes 10, or 20 MB more. |
|
@KingCrung is right. Just added swap to my EC2 micro instance as described here. Now updating dependencies works like a charm. |
|
@andremaha Perfect! Thank you!! :) |
|
I'm also getting this problem. 1GB Vagrant on a 4GB Macbook Air. Happens even when I'm limiting an update to a specific vendor. PHP Fatal error: Uncaught exception 'ErrorException' with message 'proc_open(): fork failed - Cannot allocate memory' in phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php:1033 Can solve it by vagrant halt && vagrant up && vagrant ssh, then running again. Memory usage: 102.39MB (peak: 427.97MB), time: 104.79s |
|
@adamsmeat thanks! I use your solution for my DO instance |
|
@adamsmeat - I can confirm on a stock loaded Ubuntu 12.04 512MB Digital Ocean machine that your solution is what was needed. Symfony2 is now installed and working as desired. |
|
@adamsmeat that saved my life, just added 512MB swap space on my EC2 micro instance and the problem is solved. |
|
我也遇到这样的问题，是使用vagrant box的环境，初始的内存为512M，增加到2048G后问题解决了。 |
|
encountered this problem using Digital Ocean 512MB slice...had to #945 (comment) |
|
same here @prodev42 |
|
I tried copying composer.lock unto the live server and works. with the command
|
|
@paparts Sounds like you don't versionize the |
|
Oh,I use swap solve it,thanks |
|
You can avoid this either by increasing the memory size from Or, I can be done by:
|
|
@mohitg-bs I guess you mixed something up
|
|
I solved the same problem in Vagrant. I easily Increased Memory on Vagrant Virtual Machine http://www.josheaton.org/increase-memory-vagrant-virtual-machine/ |
|
I had the same problem on a Virtual Box running through Vagrant. Config change from |
|
I have added swap memory and it solved my issue. |
|
You ran out of swap memory, try this /bin/dd if=/dev/zero of=/var/swap.1 bs=1M count=1024 |
|
To add a swap file: Determine the size of the new swap file in megabytes and multiply by 1024 to determine the number of blocks. For example, the block size of a 64 MB swap file is 65536. After adding the new swap file and enabling it, verify it is enabled by viewing the output of the command cat /proc/swaps or free. |
|
thank you! |
|
Tips - if adding swap doesn't solve the composer out of memory/couldn't allocate error:
(I'm using composer in a development environment on macOS X Sierra 10.12.4 with 16Gb RAM). |
|
Has this been resolved? I have updated the Composer globally. In addition, I created a 1GB swap space per @gillera235 suggestion. I still get the same error. What can I do to troubleshoot it? If it helps, I am using a free-tier micro EC2 instance. |
|
push the composer.lock file on your server and do composer --verbose install this way it didn't take much memory and was superfast to install the updated packges according to versions in the composer.lock file. |
|
it happens when you have less memory |
|
@sagarshah16 What happens if I don't have a mysql service? |
|
try to find which one of your running services takes more memory space. if it is not mysql. |
|
yeah ig update composer should solve the problem, sadly i update via git bash. It always throw same error to update. So to windows users just make sure use |
|
Hit the error earlier. Was on Ubuntu 16.04 on a EC2 micro instance. |
|
Just followed this link and resolved the issue. https://www.digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-16-04 |
Reference: Thank you Jeroen T. Vermeulen |
|
This issue can be exacerbated by not having memory over-commit enabled. Forking is massively inefficient without memory over-commit. Essentially when you fork, you double the committed memory usage of your current process by creating another identical process. Much of this memory is shared between the parent and child processes, but is copy-on-write, so any writes will cause the shared memory to get copied. When over-commit is enabled, your system allows this duplicated shared memory, but if you write to the shared memory, you might not have enough physical RAM to handle the copy. With over-commit disabled, your system won't allow you to allocate the memory in the first place. |
|
Getting this error with 1.4GIG available... |
|
A fix for this problem is to add swap (i.e. paging) space to the instance. Paging works by creating an area on your hard drive and using it for extra memory, this memory is much slower than normal memory however much more of it is available. To add this extra space to your instance you type: sudo /bin/dd if=/dev/zero of=/var/swap.1 bs=1M count=1024 If you need more than 1024 then change that to something higher. To enable it by default after reboot, add this line to /etc/fstab: /var/swap.1 swap swap defaults 0 0 |
Thanks so much, Instead of running Its better to than having to increase memory size in php.ini or increasing instance memory itself. |
|
Turning the swap on resolved my problem. /bin/dd if=/dev/zero of=/var/swap.1 bs=1M count=1024 |
|
How many of you will post something what was written in this thread? @jemerocay, have you read the topic? The same is posted ~10 messages above. Contributors: close this, please. |
and others
ErrorException: proc_open(): fork failed - Cannot allocate memory in phar:///var/www/workspace/MyProject/build/composer/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php on line 943
Call Stack:
0.0523 765208 1. {main}() /var/www/workspace/MyProject/build/composer/composer.phar:0
0.0528 763216 2. require('phar:///var/www/workspace/MyProject/build/composer/composer.phar/bin/composer') /var/www/workspace/MyProject/build/composer/composer.phar:15
0.0830 3504584 3. Composer\Console\Application->run() phar:///var/www/workspace/MyProject/build/composer/composer.phar/bin/composer:13
0.0865 3865984 4. Symfony\Component\Console\Application->run() phar:///var/www/workspace/MyProject/build/composer/composer.phar/src/Composer/Console/Application.php:66
31.9725 246198552 5. Symfony\Component\Console\Application->renderException() phar:///var/www/workspace/MyProject/build/composer/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php:113
31.9726 246199624 6. Symfony\Component\Console\Application->getTerminalWidth() phar:///var/www/workspace/MyProject/build/composer/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php:771
31.9726 246199784 7. Symfony\Component\Console\Application->getSttyColumns() phar:///var/www/workspace/MyProject/build/composer/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php:848
31.9727 246202984 8. proc_open() phar:///var/www/workspace/MyProject/build/composer/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php:943
31.9728 246204736 9. Composer\Util\ErrorHandler::handle() phar:///var/www/workspace/MyProject/build/composer/composer.phar/src/Composer/Util/ErrorHandler.php:0
The text was updated successfully, but these errors were encountered: