-
Notifications
You must be signed in to change notification settings - Fork 494
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
Segmentation Fault with Symfony Commands Using webdevops/php-nginx-dev:8.2 Image #523
Comments
Just tested and deactivating ionCube resolves the issue. |
Hi, On my side I have more and more of these issues (with symfony too):
I was wondering if this is the same issue, tried to disable ioncube with 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 ? |
I added this comment to #531 as well, but I'll add it here in case it helps anyone else: I was able to narrow down a segfault I've been getting to calls to Here's a script that works for me to reproduce the issue: <?php
#[Attribute()]
class Example {
public function __construct() {
}
}
class Foo {
#[Example]
public int $bar;
}
$foo = new Foo;
$reflection = new ReflectionObject($foo);
$properties = $reflection->getProperties();
foreach ($properties as $property) {
$attributes = $property->getAttributes();
foreach ($attributes as $attribute) {
$attribute->newInstance(); // Segfault here
}
}
echo 'OK' . PHP_EOL; The above script will segfault on the call to |
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: