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
Composer installer causes PHP error "CLI has stopped working" #3971
Comments
could you try : |
same error appears, PHP CLI has stopped working |
If I try even this I will close this as its obviously not a problem with the Composer installer |
OK, I think I've traced this to actually having opcache enabled on the CLI (this |
👍 opcache.enable_cli=1 |
Yeah, symphony screwed up my zip file program written in php which I run using a .bat file on windows. I run a backup everyday and I kept getting the cli message. Then I was getting error messages from my archive. and I was able to trace any new programs I installed from where I started getting errors and it was when I installed symphony which I later removed. I did a little research and its definitely a dll of some type was changed. Visual studio debugger was telling me that pdb symbol file was missing and suggested that I should use Microsoft symbols. didnt help, I did not want to upgrade my php version because its tied to apache server and I did not want to shut down and reconfigure. just not worth it at this time, Especially since the error seems to cover only one program. So I changed Zip Archive to PharData tar.gz files and no more errors. My hypothesis is that Zip Archive module shares dll file(s) that symphony overwrites. I am satisfied with the solution at this point. but there could be other modules that could be effected. |
I have an issue instlaling Comnposer.
Running php 5.6.8 (latest) on Windows 7 with opcache and xdebug 2.3.2 (latest) enabled. When I try to install composer I get a "CLI has stopped working" error.
The composer installer command I'm using is straight from the composer getting started docs.
Here are the details of the "CLI has stopped working" error from Windows:
This indicates the opcache is causing the problem, but it seems like a problem with having both opcache and xdebug enabled, as if I turn either of these extensions off the composer installer command works fine.
I've also found that Composer will still install when both opcache and xdebug are enabled, but only when not using the pipe command, e.g.
Maybe someone knows what is happening and can explain?
The text was updated successfully, but these errors were encountered: