PHP runs out of memory

[XedinUnknown]

Hi,

I'm using your class in my PHP script to make sure Composer is installed, and also to run CLI commands on it. However, when I run composer update ($wrapper->run('update', $output)), my script runs out of memory:

Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 291 bytes) in phar://path/to/my/script/composer.phar/vendor/composer/semver/src/VersionParser.php on line <b>403</b><br />

Surely, I could simply increase the PHP memory limit. However, what I can't understand is this: why is my script running out of memory? CLI commands are surely run on a different thread than my webpage. The worst case scenario would be the $output containing the PHP error text, and my page continuing to load.

Could you look into this, or at least provide some advice please?

[eviweb]

Hi @XedinUnknown,
thanks for reporting this issue.
I apologize but it will take some time before I can look at it. I'm currently confined to bed with a broken leg and only have access to my mobile phone.
Could you please give me more clue on how you use the wrapper. I presume the memory size in your php.ini is set to 128MB.
What I don't understand is why weren't you noticed about the required memory size, fixed to 512MB.
This value was originally taken from the Composer CLI script.
I will work at this issue the sooner I will be able to.
But feel free to propose a PR if you have an idea to solve it.
Best regards
Eric

[XedinUnknown]

Hi,

Sorry to hear about your injury.
Maybe I will submit a PR. For now, my idea is to make sure that the CLI
process is on a different thread, as I suspect that the threads have
somehow gotten mixed up.

Hope you get well soon. Thanks for your quick reply!

Sincerely yours,
Anton Ukhanev

On Mon, Oct 12, 2015 at 10:20 AM, eviweb notifications@github.com wrote:

Hi @XedinUnknown https://github.com/XedinUnknown,
thanks for reporting this issue.
I apologize but it will take some time before I can look at it. I'm
currently confined to bed with a broken leg and only have access to my
mobile phone.
Could you please give me more clue on how you use the wrapper. I presume
the memory size in your php.ini is set to 128MB.
What I don't understand is why weren't you noticed about the required
memory size, fixed to 512MB.
This value was originally taken from the Composer CLI script.
I will work at this issue the sooner I will be able to.
But feel free to propose a PR if you have an idea to solve it.
Best regards
Eric

—
Reply to this email directly or view it on GitHub
#9 (comment)
.

[eviweb]

Thanks for your compassion ;)
As the wrapper only delegates the command calls to Composer commands, I think investigating should be done on the Composer side.
At first sight, Composer does not seem to create new threads when performing updates.
And the last Composer version requires 1GB as minimal memory size.
I have to admit that I've never used the wrapper in a web application context.
Maybe shouldn't you use it directly in a web callable script but delegate to an asynchronous shell context script which is responsible of Composer linkage.
In that case you will be sure to work with two different threads.
It should be a lead to explore.
Feel free to share your experience, it's very interesting.
And if you find a way to improve the wrapper, please don't hesitate to submit a PR.
I will do all my best to be as reactive as I can in my current situation.

Best regards Anton,

Eric