-
-
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 Exhausted #8063
Comments
Allow Composer to use more memory. |
Frankly, i have tried in all ways you told @alcohol |
https://www.chapterthree.com/blog/how-fix-composer-memory-issue i have did exactly the same! When i execute this command i get :
i tried also this command
|
Increase your swap space. As explained elsewhere you are out of system memory so no matter how you configure PHP it's going to keep failing. |
Composer consumed more than 939 MB before it failed. If it is normal then this huge requirement should be mentioned in: https://getcomposer.org/doc/00-intro.md#system-requirements |
Consumption is based on your dependency tree and constraints. It could be 10mb. It could be 2gb. 🤷♂️ |
It's not huge. Development machines are generally considered to require at least 8GB, preferably 16GB of RAM to run memory-hungry development tools. Therefore 939MB is certainly not 'huge'. Same goes for tools like MySQL - the minimum amount to run it is like 256MB of RAM, but it's not going to be running any kind of big database like this. Add RAM as required for use case. They don't document either that MySQL could usefully use up to hundreds of gigabytes. |
I understand need for having good machine, but it is not so huge when running multi services Docker stack (with services like MySQL), all this in Docker VM and a lot of apps in host system. And it is not handy to stop everything to update composer dependencies.
… 14. 11. 2019 v 13:52, Niels Keurentjes ***@***.***>:
It's not huge. Development machines are generally considered to require at least 8GB, preferably 16GB of RAM to run memory-hungry development tools. Therefore 939MB is certainly not 'huge'.
Same goes for tools like MySQL - the minimum amount to run it is like 256MB of RAM, but it's not going to be running any kind of big database like this. Add RAM as required for use case. They don't document either that MySQL could usefully use up to hundreds of gigabytes.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#8063?email_source=notifications&email_token=AAEV6WBEHEDQRJT2O6C2PL3QTVCYLA5CNFSM4HBY2NP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEBXHUQ#issuecomment-553874386>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEV6WETWUM27V6BC5PQVHLQTVCYLANCNFSM4HBY2NPQ>.
|
That's still beside the point, being that if you don't normally have 1GB of RAM to spare you really need more in your machine. Composer is not the only devtool soaking up peak capacity. More or less offtopic but relevant - keep in mind that databases are usually intent on claiming ALL available RAM eventually in their host system, because it keeps them efficient. This is obviously not such a good idea on a development machine also running other services and IDEs, so you have to tell it explicitly not to. MySQL can run fine when constrained to 256-512MB of RAM actually, and you can easily configure that. |
I have 16 GB Ram - 6 in use, so 9-10 GB free. Nonetheless I get this error at 1405091840 bytes. |
"I have 16 GB Ram - 6 in use, so 9-10 GB free. Nonetheless I get this error at 1405091840 bytes. Me too!! |
Run |
My
composer.json
:Output of
composer diagnose
:When I run this command:
I get the following output:
The text was updated successfully, but these errors were encountered: