We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm encountering a segmentation fault when running Symfony commands using the webdevops/php-nginx-dev:8.2 image. The error message is as follows:
Program received signal SIGSEGV, Segmentation fault. 0x000055c10020b86b in zend_observer_fcall_end_all ()
Interestingly, the segmentation fault disappears when ionCube is disabled.
The text was updated successfully, but these errors were encountered:
I'm encountering a segmentation fault when running Symfony commands using the webdevops/php-nginx-dev:8.2 image. The error message is as follows: Program received signal SIGSEGV, Segmentation fault. 0x000055c10020b86b in zend_observer_fcall_end_all () Interestingly, the segmentation fault disappears when ionCube is disabled.
Just tested and deactivating ionCube resolves the issue.
Sorry, something went wrong.
Hi,
On my side I have more and more of these issues (with symfony too):
AH01067: Failed to read FastCGI header
I was wondering if this is the same issue, tried to disable ioncube with PHP_DISMOD=ioncube to see if it fix like the segfault.
PHP_DISMOD=ioncube
Thanks for the tips
Hello,
also The issue is present with the tideways module, so you may need to deactivate it too.
So sad to see these php apache images with no real support or bug fix since months.
Is there someone out there who may plan to work on improving and fixing these images please ?
No branches or pull requests
I'm encountering a segmentation fault when running Symfony commands using the webdevops/php-nginx-dev:8.2 image. The error message is as follows:
Interestingly, the segmentation fault disappears when ionCube is disabled.
The text was updated successfully, but these errors were encountered: