Segfault on PHP FPM 7.2.15 / Laravel 5.7, how to debug/proceed? #304
Labels
🐛 bug
Something isn't working
Comments
|
Hi, thanks for reporting this. We had other reports (#302) of segmentation fault with php 7.2. We are currently looking into this and we will update this issue as soon as we make progresses. |
|
Perfect, let me know if there is something I can do to provide more info / context :) |
|
Thanks :)! One question actually: which server are you using? Nginx, apache? |
|
Also, which OS? |
|
NGINX on Ubuntu 16.04. PHP is installed from: https://deb.sury.org/ (not the distro default). To be really exact in case it helps: (It's a server provisioned by Laravel Forge) |
|
Thanks, very useful 👍 ! cc @pawelchcki! |
|
Hi, we weren't able to reproduce the same issue using any of our test environments, including php-fpm and nginx/apache. So we added the possibility to log a low level stacktrace when a segfault occurs. This is included in the new release 0.13.2. In order to achieve this, the following is required:
If you could do this and provide us with such stacktrace it would be awesome. Note: please review the dump before uploading it as it may contain reserved data that you want to remove (e.g. passwords). Thanks for the patience and the help! |
|
And here it is: |
|
Hi @stayallive thanks for the info above. Super useful! cc @pawelchcki for the core dump ^^ |
|
Thanks @stayallive and @labbati - looking at it now. From first glance it looks like this error happens outside of extension code (hence the backtrace is a bit cryptic), but it already seems to point to some memory issue (in our extension), which have left the object pool in incorrect state. I'll have to take a closer look at the Thanks agian for stack trace its superuseful! |
|
Hey there, we are experiencing a similar issue, but using Laravel and using AWS's default AMI for PHP 7.2 on ElasticBeanstalk (Amazon Linux (RHEL); apache; php-fpm). No graphQL and so far only observed for one route. If i add 98-ddtrace.ini to conf.d and restart apache, the following is logged to apache error log:
|
|
Hi! We just release 0.13.4 which brings some fixes to the memory management and it is supposed to fix the segmentation faults in php-fpm 7.2. Special thanks to @stayallive for helping us debugging the memory issues in his environment! His help and guidance were of paramount importance. It would be great if you can install it in your hosts to make sure the error disappeared. |
|
Hi! I assume things are still going well on 7.2 😄. Closing this issue for now, thank you @stayallive for all the help in spotting the real underlying memory leak in out library. |
estringana
pushed a commit
that referenced
this issue
Dec 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As the title says I'm experiencing a segfault hitting our GraphQL endpoint, so far found nothing else. How do I provide enough information to be a useful report?
The text was updated successfully, but these errors were encountered: