-
Notifications
You must be signed in to change notification settings - Fork 69
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
Very high occurrence of segmentation faults in production using PHP FPM - unable to use it #634
Comments
I can confirm we are seeing the same behavior on 1.4.2 |
@pjaak @MattBred Could you please check if you still experiencing the issue with the latest release (v.16) and if so could you please share a simple docker image definition that reproduces this issue? |
Sorry @SergeyKleyman we're not going to be running this in production for the forseeable future, and that is where I noticed the issue occur. Edit: Sorry I didn't mean to close with comment. |
Hi @SergeyKleyman , |
We are also seeing this problem on AMD64 with v1.5.2 but only with some requests, will also give 1.6.x a try. |
EDIT: This is not true, segfaults seems to be happening in a different (later) place so the page I'm testing with renders but PHP FPM still crashes. |
Describe the bug
Verison: 1.4.2
System: Ubuntu 20.04 ARM64 (AWS graviton)
I was getting a segfault in my PHP FPM logs every 1-3 minutes. I confirmed its from the Elastic APM agent, because when I turn the extension off, the segfaults stop. When I turn it back on, they happen again.
Unfortunately, I can not use the extension as it is causing way too many errors on production..
I dumped the core and looked at the backtrace with GDB. It looks like an infinite loop/recursion? The entire stack trace is this on repeat, 34000 lines long.
This is the beginning of the trace:
My Elastic APM config is:
To Reproduce
I cannot say - it was happening every 1-3 minutes on production.
Expected behavior
Not to segfault.
The text was updated successfully, but these errors were encountered: