View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002342 | Xdebug | Tracing | public | 2025-04-27 08:30 | 2025-07-08 21:24 |
Reporter | thecrypto | Assigned To | derick | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | assigned | Resolution | open | ||
Product Version | 3.4.2 | ||||
Summary | 0002342: Segfault in PHP-FPM on Alpine when xdebug.start_with_request=yes and calling StripeClient->subscriptions->all() | ||||
Description | Running Xdebug 3.4.2 on PHP 8.4.6-fpm-alpine3.21 (Docker). As soon as xdebug.start_with_request = yes is set, any call to \Stripe\StripeClient->subscriptions->all(...) crashes the FPM worker with SIGSEGV inside Xdebug’s trace_textual.c::add_arguments. Other endpoints (e.g. customers->all()) complete normally. Changing xdebug.start_with_request to no (even with trace still enabled) eliminates the crash. | ||||
Steps To Reproduce |
| ||||
Additional Information | • Only subscriptions->all() triggers the crash | ||||
Tags | alpine, bug, php-fpm, segfault, stripe-php, tracing, xdebug | ||||
Operating System | Alpine 3.21 (Docker) | ||||
PHP Version | 8.4-dev | ||||
|
Apologies, please disregard previous zip as it was missing php.ini and an empty vendor folder required for the docker compose file. Please use this instead to easily reproduce the segmentation fault. |
|
docker compose up was still running after 1000 seconds. I aborted it. Can you come up with something smaller? |
|
Hi Derick, Would you be kind enough to share more information of the issue? I ran this docker-compose command on WSL with Docker Desktop on Windows when I compiled it and now I've just the zip content on MacOS on an M3 with Docker Desktop for Mac, and that docker-compose commands worked on both, it took about 30-40 seconds to build and then ran fine. |
|
I don't have more information. It just took a really long time — and it was too long for me to wait for it. I now ran it again, and it was done in 81 seconds. |
|
In any case, it doesn't crash anything here: |
|
I tried adding valgrind to the Dockerfile, and now when I run |
|
Would you have time to provide the requested feedback or information? |
|
Sorry Derick been extremely busy myself working on a SaaS launch. I'll try to find some spare time over the next week or two to try this on a fresh Stripe account to see if the error goes away. Rebuilding the image should not be an issue, if you are using docker desktop, you should be able to remove any old/lingering images, allowing a fresh image to be created is likely the better outcome here, once I get more time hopefully I can emulate what you are doing to see what is going on. Thanks Derick! |
Date Modified | Username | Field | Change |
---|---|---|---|
2025-04-27 08:30 | thecrypto | New Issue | |
2025-04-27 08:30 | thecrypto | Tag Attached: alpine | |
2025-04-27 08:30 | thecrypto | Tag Attached: bug | |
2025-04-27 08:30 | thecrypto | Tag Attached: php-fpm | |
2025-04-27 08:30 | thecrypto | Tag Attached: segfault | |
2025-04-27 08:30 | thecrypto | Tag Attached: stripe-php | |
2025-04-27 08:30 | thecrypto | Tag Attached: tracing | |
2025-04-27 08:30 | thecrypto | Tag Attached: xdebug | |
2025-04-27 22:14 | thecrypto | Note Added: 0007263 | |
2025-04-27 22:14 | thecrypto | File Added: docker-sample-250428.zip | |
2025-05-02 10:36 | derick | Assigned To | => derick |
2025-05-02 10:36 | derick | Status | new => feedback |
2025-05-02 10:36 | derick | Note Added: 0007272 | |
2025-05-02 12:09 | thecrypto | Note Added: 0007279 | |
2025-05-02 12:09 | thecrypto | Status | feedback => assigned |
2025-05-07 13:58 | derick | Note Added: 0007282 | |
2025-05-07 14:01 | derick | Note Added: 0007283 | |
2025-05-07 14:06 | derick | Note Added: 0007284 | |
2025-05-07 14:06 | derick | Status | assigned => feedback |
2025-06-27 00:19 | derick | Note Added: 0007328 | |
2025-07-08 21:24 | thecrypto | Note Added: 0007331 | |
2025-07-08 21:24 | thecrypto | Status | feedback => assigned |