Endless sitemap generation

[AlbertoSinigaglia]

Recently I updated my website to support more than 1 language, and the indexable page went from 1100 to 3300.
Until this update, everything went fine, no issue at all, but not whenever i run php artisan sitemap:generate i have to wait something like half an hour, and then it either get killed, or prints:

 Symfony\Component\Debug\Exception\FatalErrorException  : Allowed memory size of 134217728 bytes exhausted (tried to allocate 2097184 bytes)

  at .../vendor/guzzlehttp/psr7/src/Stream.php:228
    224|         if (0 === $length) {
    225|             return '';
    226|         }
    227| 
  > 228|         $string = fread($this->stream, $length);
    229|         if (false === $string) {
    230|             throw new \RuntimeException('Unable to read from stream');
    231|         }
    232| 


   Whoops\Exception\ErrorException  : Allowed memory size of 134217728 bytes exhausted (tried to allocate 2097184 bytes)

  at ...vendor/guzzlehttp/psr7/src/Stream.php:228
    224|         if (0 === $length) {
    225|             return '';
    226|         }
    227| 
  > 228|         $string = fread($this->stream, $length);
    229|         if (false === $string) {
    230|             throw new \RuntimeException('Unable to read from stream');
    231|         }
    232| 

  Exception trace:

  1   Whoops\Run::handleError("Allowed memory size of 134217728 bytes exhausted (tried to allocate 2097184 bytes)", ".../vendor/guzzlehttp/psr7/src/Stream.php")
      ...vendor/filp/whoops/src/Whoops/Run.php:454

  2   Whoops\Run::handleShutdown()
      [internal]:0

So my questions are:

1. are there a "verbose mode" to check whether it goes into a cycle and so never ends?
2. is "increasing memory" the real solution to this problem?
3. this memory size is the one I can find in the php.ini file?

thank you

[freekmurze]

There is no real verbose mode, you'll have to put dump statements to investigate yourself. I cannot answer 2) and 3) for you.

Please PR improvements should you find that this package contains the root cause of the error.