Memory leak on import command

[michnovka]

Despite #351 I still get

  Error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 86016 bytes)  

after importing larger DB.

Indexed a batch of 500 / 500 App\Entity\Log\CronLog entities into app_dev_cron_logs index (268000 indexed since start)
PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 86016 bytes) in /var/www/dockontrol/vendor/meilisearch/meilisearch-php/src/Http/Serialize/Json.php on line 18
14:01:41 CRITICAL  [php] Fatal Error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 86016 bytes) ["exception" => Symfony\Component\ErrorHandler\Error\OutOfMemoryError^ { …}]

In Json.php line 18:
                                                                                           
  Error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 86016 bytes)  
                                                                                           

I believe there has to be a memory leak, as each row of this CronLog has NO references to other tables

[norkunas]

Not sure. Could you track down if this is related to doctrine itself?
Do you run your command with debug enabled? Does it work with --no-debug ?

[maciekpaprocki]

I had the same issues when running on dev. Doctrine is leaky on dev even when removing logging middlewares. That just seems to be the case for now as symfony/doctrine issues are full of problems with it too.

There's not much this library can do.

If you still see the issues on prod, I would recommend checking your normaliser/queries run ( doctrine might be loading loads of extra info )