carbontwelve revised this gist 1 month ago. Go to revision
1 file changed, 9 insertions
PHP-gRPC.md(file created)
| @@ -0,0 +1,9 @@ | |||
| 1 | + | Since [PHP added stack size checking in 8.3](https://www.php.net/manual/en/migration83.other-changes.php#migration83.other-changes.ini) the current stable versions of [gRPC available through pecl](https://pecl.php.net/package/gRPC) have been triggering it with the following error becoming a familair sight in reporting platforms. | |
| 2 | + | ||
| 3 | + | > Maximum call stack size of 10436608 bytes (zend.max_allowed_stack_size - zend.reserved_stack_size) reached. Infinite recursion? | |
| 4 | + | ||
| 5 | + | One workaround reported in [issue 584 for `googleapis/gax-php`](https://github.com/googleapis/gax-php/issues/584) is to set `zend.max_allowed_stack_size: -1` in order to disable PHPs new stack size validation, however the fact its in place to avoid segfaulting means turning it off isn't an adequate long term solution! | |
| 6 | + | ||
| 7 | + | The bug was reported on May 7th, 2025 in [issue 39509 for `grpc/grpc`](https://github.com/grpc/grpc/issues/39509) and there is a lot of community discussion in that thread but zero estimated timeline for a bugfix from the project maintainers. | |
| 8 | + | ||
| 9 | + | GitHub user **inrdkec** [commented](https://github.com/grpc/grpc/issues/39509#issuecomment-3083767511) that rolling back to 1.67.0 seems to solve the issue and that is exactly what I have done at work. | |
Newer
Older