…#142)

Triggering the garbage collector after the request has been handled and
when the worker may be idle prevents the garbage collection from being
randomly done in the middle of the handling of a request (which delays
the delivery of the HTTP response).

Another option, that is done by Laravel Octone, is to trigger the GC
when a configurable amount of memory has been consumed instead of after
every request.
I think this patch is good enough for FrankenPHP as usually many workers
will be available.

Follows symfony/symfony#52079.

Backport of some micro-optimizations by @francislavoie
laravel/octane#764 (comment)

---------

Co-authored-by: Francis Lavoie <lavofr@gmail.com>

Tiny refactoring as suggested in
php-runtime/runtime#148 (comment)

…client is aborted (#155)

See dunglas/frankenphp#316 and
dunglas/frankenphp#310 (comment).

See dunglas/frankenphp#280.

This will fix #157

Fixes the issue that the loop doesn't exist when `$loopMax` is reached,
but `$loopMax+1`. Please refer to
php-runtime/runtime#173 for details.

Use the new
[`xdebug_connect_to_client()`](https://xdebug.org/docs/all_functions#xdebug_connect_to_client)
function if available to allow debugging with Xdebug in worker mode.