-
-
Notifications
You must be signed in to change notification settings - Fork 259
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
SIGSEGV: segmentation violation. Invalid memory address or nil pointer dereference #1269
Comments
Are you using version 1.3.4? If yes could you try downgrading to v1.3.3? Regarding the backtrace, I fear it's an issue introduced with the refactoring of worker threads (#1137). cc @AlliBalliBaba |
You are right @dunglas. I have downgraded to v1.3.3 and it works ok. Will wait for v1.3.5 to switch back to |
Do you have any environment variable or HTTP header containing an empty string? I think my patch will fix the issue, but I don't manage to reproduce it currently (I would like to add a test ensuring that the patch works). |
No, there are no empty variables if I use Maybe there is some issue with some characters if the env value contains some special symbols. I have a variable containing JSON with special characters, but probably not as locally it runs ok. Here is the output of
|
I published a new release that will soon be available: https://github.com/dunglas/frankenphp/actions/runs/12433328417 I hope it will fix the issue. |
``Still get it with Edit: Here's the output from the logs.
|
This happens immediately after starting the server? Are you using the worker with symfony or laravel? Are you explicitly using |
Yes.
Symfony.
Yes! |
Ok that's |
Oh I think you're right @dunglas |
32 threads and 30 workers. Those numbers are provided with two env vars... With a default to 3 and 2. Was just in the process of doing performance testing and trying out different configs and resource allocation. Will check for the file when I get back home :) |
Closed by #1278 |
For me the issue still persists after upgrading to In my case it seems related to opcache preloading, when its enabled the server immediately crashes:
Framework: Symfony |
#1278 is not in 1.3.5. It will be in the upcoming 1.3.6 version. |
I think a build job failed so no changes were pushed for 1.3.6 to dockerhub 🙈 Edit: I tested it with the dev build that ran shortly after, |
The 1.3 tag wasn't updated yet to 1.3.6 :) |
Tested with 1.3.6 version, works as expected. |
Same for me. Thanks everyone. happy holidays :) |
What happened?
The container started to crash after recent deploy and I'm receiveng
SIGSEGV: segmentation violation
today. I believe it may be related to the fact that I wanted to increase memory_limit to3.5G
or3584M
. It may also be linked to the fact that there is an env variable which is very long 7700 chars. Or maybe it's related to the new PHP version? Locally it works ok but fails when deployed to Azure Container Apps.Build Type
Docker (Debian Bookworm)
Worker Mode
Yes
Operating System
GNU/Linux
CPU Architecture
x86_64
PHP configuration
Relevant log output
The text was updated successfully, but these errors were encountered: