[jit] doctrine migrations behave weird and result in random errors and hanging processes

Description

The following code: https://github.com/verfriemelt-dot-org/doctrine-migrations-repro

Resulted in this output:

$ php -d opcache.jit=on bin/console doc:mi:mi -vv --no-interaction
[notice] Migrating up to DoctrineMigrations\Version_1000
[info] ++ migrating DoctrineMigrations\Version_0001
[debug] CREATE TABLE tab_0001 ()
[info] Migration DoctrineMigrations\Version_0001 migrated (took 22.3ms, used 10M memory)
[info] ++ migrating DoctrineMigrations\Version_0002

***hangs at 100% cpu***

or fails with strange errors instead. disabling jit does solve the issue. check out the reproducer, which results in the hanging process, on a private project it fails with

In TableDoesNotExist.php line 16:

  [Doctrine\DBAL\Schema\Exception\TableDoesNotExist]
  There is no table with name "customer_anonymisation_request" in the schema.


Exception trace:
  at ./core/vendor/doctrine/dbal/src/Schema/Exception/TableDoesNotExist.php:16
 Doctrine\DBAL\Schema\Exception\TableDoesNotExist::new() at ./core/vendor/doctrine/dbal/src/Schema/Schema.php:226
 Doctrine\DBAL\Schema\Schema->getTable() at ./core/vendor/doctrine/dbal/src/Schema/Comparator.php:64
 Doctrine\DBAL\Schema\Comparator->compareSchemas() at ./core/vendor/doctrine/migrations/src/Provider/DBALSchemaDiffProvider.php:53
 Doctrine\Migrations\Provider\DBALSchemaDiffProvider->getSqlDiffToMigrate() at ./core/vendor/doctrine/migrations/src/Provider/LazySchemaDiffProvider.php:90
 Doctrine\Migrations\Provider\LazySchemaDiffProvider->getSqlDiffToMigrate() at ./core/vendor/doctrine/migrations/src/Version/DbalExecutor.php:144
 Doctrine\Migrations\Version\DbalExecutor->executeMigration() at ./core/vendor/doctrine/migrations/src/Version/DbalExecutor.php:72
 Doctrine\Migrations\Version\DbalExecutor->execute() at ./core/vendor/doctrine/migrations/src/DbalMigrator.php:87
 Doctrine\Migrations\DbalMigrator->executePlan() at ./core/vendor/doctrine/migrations/src/DbalMigrator.php:54
 Doctrine\Migrations\DbalMigrator->executeMigrations() at ./core/vendor/doctrine/migrations/src/DbalMigrator.php:134
 Doctrine\Migrations\DbalMigrator->migrate() at ./core/vendor/doctrine/migrations/src/Tools/Console/Command/MigrateCommand.php:225
 Doctrine\Migrations\Tools\Console\Command\MigrateCommand->execute() at ./core/vendor/symfony/console/Command/Command.php:291
 Symfony\Component\Console\Command\Command->run() at ./core/vendor/symfony/console/Application.php:1092
 Symfony\Component\Console\Application->doRunCommand() at ./core/vendor/symfony/framework-bundle/Console/Application.php:123
 Symfony\Bundle\FrameworkBundle\Console\Application->doRunCommand() at ./core/vendor/symfony/console/Application.php:356
 Symfony\Component\Console\Application->doRun() at ./core/vendor/symfony/framework-bundle/Console/Application.php:77
 Symfony\Bundle\FrameworkBundle\Console\Application->doRun() at ./core/vendor/symfony/console/Application.php:195
 Symfony\Component\Console\Application->run() at ./core/bin/console:100

which is completly unrelated to the migration, so i expect this to be a jit bug rather than a bug in doctrine 🤔

PHP Version

php -v
PHP 8.5.3 (cli) (built: Feb 13 2026 15:50:47) (NTS)
Copyright (c) The PHP Group
Built by Debian
Zend Engine v4.5.3, Copyright (c) Zend Technologies
    with Xdebug v3.5.0, Copyright (c) 2002-2025, by Derick Rethans
    with Zend OPcache v8.5.3, Copyright (c), by Zend Technologies

Operating System

debian sid

Inizia dal progetto doctrine-migrations-repro collegato ed esegui il comando bin/console doc:mi:mi fornito con PHP 8.5.3 e opcache.jit abilitato, quindi confrontalo con JIT disabilitato. Traccia il malfunzionamento dal percorso OPcache JIT attraverso le voci dello stack delle migrazioni e stabilisci una causa riproducibile specifica di JIT per il blocco o l’errore di schema non correlato.