Using Doctrine entities as Module arguments causes memory leaks

Background:

We have a fairly big project using Codeception. Recently, the memory usage during tests reached around ~2 GB of memory, resulting in exceeding the limit on CI test runs.

We have managed to pin down the issue to the fact that we were using Doctrine entities as arguments in a lot of module methods when creating fixture data.

The problem stems from persistent collections - all of them have Entity Manager injected into them and Codeception stores all arguments used in module methods. This caused the old instances of entity manager service not being cleared up and memory usage steadily piling up.

We were not using the Doctrine module, since it was too troublesome due to the persistent EntityManager service.

Solution:

The only way to correctly resolve it was to use scalar data instead of full entities. This has drastically reduced memory usage.

This is not something that I would expect the Codeception team to resolve, but I think that in the section of the Doctrine module you could provide a paragraph or two warning people about this issue. It can save someone folks a lot of work.

Cheers

Comienza por localizar la documentación del módulo Doctrine y la sección que describe los argumentos de los métodos del módulo o la configuración de fixtures. Añade una advertencia de que las entidades de Doctrine pueden conservar colecciones persistentes y Entity Managers cuando se almacenan como argumentos, y recomienda usar datos escalares cuando corresponda; se considera completado cuando la indicación está documentada claramente.

Escrito por el modelo de indexación a partir del texto del issue.