相关文章推荐
重情义的毛巾  ·  module 'win32gui' has ...·  4 月前    · 
无邪的芹菜  ·  nginx http_upgrade - ...·  1 年前    · 
爱热闹的打火机  ·  RedissonClient命令 ...·  1 年前    · 
Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

Fatal error: Allowed memory size of 1610612736 bytes exhausted but already allocated 1.75G [duplicate]

Ask Question Fatal Error: Allowed Memory Size of 134217728 Bytes Exhausted (CodeIgniter + XML-RPC) (36 answers)
Closed 5 days ago .

I keep getting this memory error

PHP Fatal error:  Allowed memory size of 1610612736 bytes exhausted 
(tried to allocate 67108864 bytes) in 
phar:///usr/local/bin/composer/src/Composer/
   DependencyResolver/Solver.php on line 220

I have tried everything. Increased the memory limit a few times already. I've redownloaded composer and composer.phar. I cloned my repo on a fresh install and the first composer install worked. For some reason every attempt after causes this error.

I even removed any differences in files from the master branch and my branch that could be causing this.

PhP version 7.1.25 Composer version 1.7.2

Code I edited in a config.yml file

create_course_space_whitelist_expression: '"staff" in affiliations or 
"employee" in affiliations or "faculty" in affiliations or "guest" in 
affiliations or "GR" in student_level'

old code:

create_course_space_whitelist_expression: '"staff" in affiliations or 
"employee" in affiliations or "faculty" in affiliations or "guest" in 
affiliations

Not sure where else to look. I updated two created files within Vendor but I'm deleting vendor before running composer install

EDIT:

I've been able to narrow down the cause. composer install works fine the when working with a clean version of the repo branch. However, when any change is made to the composer.json file, it fails

We also need to see the code you are executing that results in this error, you could have problems with your code, such as an infinite loop, etc. – Jonathan Dec 21, 2018 at 0:04 You don't. That's why I'm asking to post the code that is being run for this page. (Example: your controller, any function, etc). – Jonathan Dec 21, 2018 at 0:10 @Jonathan I got the impression they were getting this error when they ran composer install, not necessarily from code they wrote – Don't Panic Dec 21, 2018 at 0:16 what about windows? i use windows 10 and this command worked for me, php -d memory_limit=-1 "C:\ProgramData\ComposerSetup\bin\composer.phar" update – saber tabatabaee yazdi May 24, 2020 at 22:07 According to @sabertabatabaeeyazdi comment php -d memory_limit=-1 "C:\ProgramData\ComposerSetup\bin\composer.phar" update will work for windows – TarangP Jul 16, 2022 at 13:55 happy to help 1.4 millions of people that stackexchange estimates in my profile 2.4 million !!! im sorry 2.4 is correct @MohamedRaza – saber tabatabaee yazdi Dec 13, 2020 at 17:34

Update Composer to version 2 and it will resolve this issue automatically.

composer self-update --2

Note : argument --2 is optional. it will upgrade the current composer version to 2 only. Without it, the composer will update to the latest version (it's the same version 2 currently but in future, it may be 3)

That solved the problem on Windows 10 with xampp installed. Do you have any idea what was this about? Thanks anyway! – Mycodingproject Jan 1, 2021 at 12:50 @Mycodingproject : Thanks for the comment. Honestly, I don't have much idea but it seems there is a bug on Composer causing the memory to be exhausted by run composer install or composer update. – Ravi Hirani Jan 13, 2021 at 0:47 Using MAMP 6.6.4 on macOS Monterey, and this worked for me. Just run composer self-update without any other parameters. – uotonyh Dec 7, 2022 at 19:07