-
-
Notifications
You must be signed in to change notification settings - Fork 229
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
Standalone binary app Stop working / Freeze after running the app for few times #858
Comments
Could you please:
Thank you! |
This bug is very real and was likely introduced in v1.1.5 ! @dunglas Reproducing the bug
Then: Page loads fine, but CTRL+R a few times quickly, the bug manifests itself as the dreaded spinning worm, and frankenphp no longer serving requets. Triggers when doing some work, THEN sending output to the client. Only tested normal PHP mode. Caddy can still be shut down, but otherwise it will no longer respond to PHP requests. Versions tested
In the short term people should stick to v1.1.4 to avoid this. Tested on Ubuntu Linux 24.04 |
Thank you very much. I'll take a look. This can be a bug in FrankenPHP itself or a new version of an extension. Could you check, for instance by using the Docker image instead of the static binary, if the issue persists with all extensions disabled? |
The only thing I can think of in the changelog that may cause the issue is "feat: add ftp, gettext, gmp, imagick, mbregex, parallel, protobuf, shmop, soap, ssh2, sysmsg, sysvshm, tidy, xlswriter, yaml and zstd extensions to the static builds", which would confirm this theory. The next step is to identify and fix (or unbundle) the buggy extension. |
I managed to reproduce the issue but didn't get a stack trace because the program freezes but doesn't crash. I'll try to disable the extensions that have been added in 1.1.5 one by one to find the offending one. |
I updated the frankenphp version to 1.2.0 but the application still hangs. Updating didn't solve the problem. Please check. Logs: 5 goroutine 19 gp=0xc000102540 m=nil [GC scavenge wait]: |
Yes, we have to revert #773. In the meantime, compiling a custom binary with |
The offender is parallel. I'm working on a patch to remove this extension. |
The problem has been reported upstream and parallel has been unbundled from FrankenPHP. krakjoe/parallel#308 |
Can confirm the issue no longer exists in 1.2.1 thank you very much tracking this down and for the quick resolution @dunglas !! |
Hey @skmirajbn 👋 can you also confirm that with FrankenPHP 1.2.1 the segfaults are gone? I see you are using I just want to make sure if this PR has anything todo with Happy to hear from you. |
First, I was thinking about that, even I select the extensions but the bugs are still there. After removing the parallel at 1.2 version I can see the freeze problem is fixed. |
Can you confirm that you had |
I could reproduce and find the problem. krakjoe/parallel#313 |
What happened?
I created the Self-contained binary using Frankenphp of my Laravel app.
The binary is created successfully and running fine. But the problem I noticed is that after handling a number of requests it hangs out.
The browsers keep loading but nothing is loaded. Until I restart the container the problem don't fix. At first I thought it was the problem of the docker but I checked another app on docker which ran smoothly.
I noticed that if there concurrent requests then it hangs earlier and once hangs it remains unresponsive until restarts.
Here I created the binary file using this dockerfile and docker compose file
FROM --platform=linux/amd64 dunglas/frankenphp:static-builder as builder
Using the below code I generated the binary inside the image
Then I extracted the binary file and used this docker compose to run the app in environment
Sometimes the get restarts which is fine but when it handle no extra line printed on terminal so I am not including any terminal logs.
Can anyone have any information how to fix it?
Build Type
Standalone binary
Worker Mode
Yes
Operating System
Other (tell us more in the description)
CPU Architecture
x86_64
PHP configuration
Relevant log output
The text was updated successfully, but these errors were encountered: