-
Notifications
You must be signed in to change notification settings - Fork 199
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
Core dumped with opentelemetry extension in symfony app in php 8.4 #1504
Comments
Can you check if you have JIT enabled? Opcache being a condition for failure makes me think it could be this bug: php/php-src#14841 |
Hi, Here our php settings ouput for any $ php -i | grep -i jit
auto_globals_jit => On => On
PCRE JIT Support => enabled
PCRE JIT Target => x86 64bit (little endian + unaligned)
pcre.jit => On => On
JIT => Disabled
opcache.jit => disable => disable
opcache.jit_bisect_limit => 0 => 0
opcache.jit_blacklist_root_trace => 16 => 16
opcache.jit_blacklist_side_trace => 8 => 8
opcache.jit_buffer_size => 64M => 64M
opcache.jit_debug => 0 => 0
opcache.jit_hot_func => 127 => 127
opcache.jit_hot_loop => 64 => 64
opcache.jit_hot_return => 8 => 8
opcache.jit_hot_side_exit => 8 => 8
opcache.jit_max_exit_counters => 8192 => 8192
opcache.jit_max_loop_unrolls => 8 => 8
opcache.jit_max_polymorphic_calls => 2 => 2
opcache.jit_max_recursive_calls => 2 => 2
opcache.jit_max_recursive_returns => 2 => 2
opcache.jit_max_root_traces => 1024 => 1024
opcache.jit_max_side_traces => 128 => 128
opcache.jit_max_trace_length => 1024 => 1024
opcache.jit_prof_threshold => 0.005 => 0.005 I understand, that in php 8.4 the default settings were changed: https://php.watch/versions/8.4/opcache-jit-ini-default-changes After your message, I tried setting it to the default settings from before 8.4, but without success.
|
Hey
I'll try to get debug symbols and will continue investigation. I was trying with |
Hi, thank you for your analysis. I managed to get similar results by building the upstream php container myself with debug symbols. I don't see anything from opentelemetry as well:
It would be really great if someone can assist me in understanding the information we have here. That would help me create an issue in the right project and hopefully find the root cause to this incompatibility between opentelemetry and said project. |
Hi,
Very difficult to give you more information without give you the app, but if I can help, don't hesitate to ping me |
Describe your environment We have an older symfony application where we want to introduce opentelemetry. We are in the middle of testing phase during which we upgraded production from php 8.3.15 to php 8.4.3. After the upgrade, our opentelemetry branch app breaks on every web request enabled:
child 24 exited on signal 11 (SIGSEGV) after 64.931337 seconds from start
.Steps to reproduce
I created a minimal Dockerfile which reproduces the behavior:
It does not break if:
PHP_VERSION=8.3.15
opcache.preload
is disabledWhat is the expected behavior?
A web request results in the default page as no routes are configured
What is the actual behavior?
A web request results in an error page, stating:
# unable to fetch the response from the backend: unexpected EOF
Container logs:
Additional context
The application does not break immediately or on cache preloading. It just breaks on every web request which fpm recovers from.
The text was updated successfully, but these errors were encountered: