After upgrade from 2.5.7 to >= 2.6.0 it uses a lot of memory during tests

[nightio]

After upgrading from 2.5.7 to >= 2.6.0 I noticed tests fail due to out of memory (standard 128M).
In the previous version my tests used up to ~100M of memory, meanwhile, after the upgrade it needs ~400M of memory.

After a downgrade to 2.5.7, it returned to normal.

I have tested all 2.6.x versions and the result is the same. So the problem raised in version 2.6.0

Temporary fix: lock version 2.5.7 composer require doctrine/doctrine-bundle:2.5.7

[dmaicher]

Can you provide a reproducer that shows this increased memory usage? Did not notice anything strange on my apps.

[ostrolucky]

Did you upgrade only doctrine-bundle? Please make sure you only update bundle to isolate the problem.

[nightio]

@ostrolucky

Did you upgrade only doctrine-bundle? Please make sure you only update bundle to isolate the problem.

Yes, I did. I updated all packages to the newest ones and ran the tests. It turns out it uses a lot of memory. I started downgrading ONLY the doctrine/doctrine-bundle package and in version 2.5.7 it backed to normal.

@dmaicher I will try to make some examples as I find some time.

[dmaicher]

Closing here for now. Let me know if you can provide a reproducer @nightio then we can take a look and re-open if needed.

[Kodzila]

I'm experiencing the same issues. I will also look for some clues, but letting you know it's not the single project problem.

Edit: I found the issue, but it's only a side effect of change in this bundle. In 2.6.0 there was an introduction of Logger Middleware: #1429. This is fine, but it creates a bad synergy with Codeception framework plus Symfony module https://codeception.com/docs/modules/Symfony.

In the module, doctrine service is persisted between tests which effectively freezes the dependencies for Doctrine, including logger which is passed to the Driver. Logger is not cleared between tests, which makes record being accumulated and eventually leads to memory overflow.

[nightio]

@dmaicher I have prepared the repo with reproducing of this issue
https://github.com/nightio/DoctrineBundle-issues-1525

Note that the problem comes out with dama/doctrine-test-bundle in my case.
However with the same version of dama/doctrine-test-bundle but a different version of doctrine bundle problem exists or not (exists on 2.6.x but not on 2.5.7)

[dmaicher]

Thanks for the nice reproducer @nightio. I will take a closer look.

[dmaicher]

This is actually not an issue with DoctrineBundle.

Its an issue with dama/doctrine-test-bundle instead. There is a memory leak that only shows up when using the new Doctrine DBAL logging middleware which is active since DoctrineBundle 2.6.x.

As a workaround you can disable DBAL logging in tests:

when@test:
    doctrine:
        dbal:
            logging: false

I will create a new issue on dama/doctrine-test-bundle and will try to look into fixing it there.