Repository navigation
XdebugHandler->check() should be called very early #175
Description
I did some testing with xdebug-handler. my test.php looks like
<?php
use Composer\XdebugHandler\XdebugHandler;
require_once __DIR__ . '/vendor/autoload.php';
var_dump(extension_loaded('xdebug'));
echo "booting a second...\n";
sleep(1);
$xdebug = new XdebugHandler('myapp');
$xdebug->check();
unset($xdebug);
var_dump(extension_loaded('xdebug'));
echo "running a second...\n";
sleep(1);what I realized is, that the logic which is running before $xdebug->check(); is executed twice.
➜ xdebug-handler git:(pcntl_exec) ✗ php test.php
bool(true)
booting a second...
bool(false)
booting a second...
bool(false)
running a second...
this means a application should invoke $xdebug->check(); very very early in the process, because the bootstrap logic is executed twice in the restarting case.
if you e.g. have a symfony-console application and do the $xdebug->check(); only after the command has been determined and dispatched, I can see PHPStan is loosing ~0.04seconds in the process. this might easily add more time when you take this perf hit on every worker-process along the way.
I wonder whether thats something which need to be documented somewhere.
Activity
[-]`XdebugHandler->check()` should be verify early[/-][+]`XdebugHandler->check()` should be called very early[/+]johnstevenson commentedon Oct 18, 2026
Err, well yes, it would have to.
It depends what the application wants to do though and whether it needs certain information before it can decide. The readme contains a simplified example which does not restart on a help command https://github.com/composer/xdebug-handler#example
It also points to some Examples that are used in the functional tests but can also be run independently to illustrate the behaviour in different scenarios. So you could use
app-basic.phpinstead of your test script: