Skip to content
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

Using Fibers causes epic crash #46

Open
withinboredom opened this issue Oct 20, 2022 · 5 comments · May be fixed by #387 or #171
Open

Using Fibers causes epic crash #46

withinboredom opened this issue Oct 20, 2022 · 5 comments · May be fixed by #387 or #171
Labels
bug Something isn't working

Comments

@withinboredom
Copy link
Collaborator

withinboredom commented Oct 20, 2022

Minimal code to reproduce:

<?php

do {
    $running = false;
    //$running = frankenphp_handle_request(function (): void {
        $fiber = new Fiber(function() {
            echo "Starting Fiber\n";
        });
        $fiber->start();
    //});
} while ($running);

With some slight modifications, it can also be reproduced in worker mode.

@dunglas dunglas added the bug Something isn't working label Oct 21, 2022
krakjoe added a commit to krakjoe/frankenphp that referenced this issue Nov 10, 2022
  This is the bare minimum required to make fibers work within the go
  runtime.
krakjoe added a commit to krakjoe/frankenphp that referenced this issue Nov 10, 2022
  This is the bare minimum required to make fibers work within the go
  runtime.
krakjoe added a commit to krakjoe/frankenphp that referenced this issue Nov 10, 2022
  This is the bare minimum required to make fibers work within the go
  runtime.
dunglas pushed a commit that referenced this issue Aug 4, 2023
  This is the bare minimum required to make fibers work within the go
  runtime.
@dunglas dunglas linked a pull request Aug 4, 2023 that will close this issue
@dunglas dunglas pinned this issue Aug 6, 2023
dunglas pushed a commit that referenced this issue Aug 16, 2023
  This is the bare minimum required to make fibers work within the go
  runtime.
dunglas pushed a commit that referenced this issue Sep 8, 2023
  This is the bare minimum required to make fibers work within the go
  runtime.
@withinboredom
Copy link
Collaborator Author

withinboredom commented Dec 13, 2023

@dunglas the following Docker file (props @cdaguerre in #374) appears to "fix" fibers. At least for this reproducer with manual testing. It needs more testing:

FROM dunglas/frankenphp:latest-builder-php8.3-alpine AS builder

COPY --from=caddy:builder-alpine /usr/bin/xcaddy /usr/bin/xcaddy

ENV CGO_ENABLED=1 XCADDY_SETCAP=1 CGO_CXXFLAGS=-fPIE CGO_CFLAGS=-fPIE CGO_LDFLAGS=-pie XCADDY_GO_BUILD_FLAGS='-buildmode=pie -ldflags="-w -s" -trimpath'
RUN xcaddy build \
    --output /usr/local/bin/frankenphp \
    --with github.com/dunglas/frankenphp=./ \
    --with github.com/dunglas/frankenphp/caddy=./caddy/ \
    --with github.com/dunglas/mercure/caddy \
    --with github.com/dunglas/vulcain/caddy

🥳 🤞 🤞 still testing...

@dunglas
Copy link
Owner

dunglas commented Dec 13, 2023

Great news! Don't hesitate to open a PR with this changes, so we can see if this fix the issue for all architectures.

@withinboredom
Copy link
Collaborator Author

I'll do some proper testing by Monday (by updating the fiber branch), but I haven't seen a crash yet via manual testing.

@piotrekkr
Copy link

@withinboredom I had issues with fibers so I could also test this on my Cloud Run service but not really sure where can I get docker image to use with this fix.

@withinboredom
Copy link
Collaborator Author

withinboredom commented Jan 10, 2024

It doesn't fix it, per se, more-or-less just reduces the probability of a crash.

Edit to add: the best way to prevent a crash is to just not output anything at all inside a fiber.

dunglas pushed a commit that referenced this issue Jan 14, 2024
  This is the bare minimum required to make fibers work within the go
  runtime.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants