* Increase reserved memory for error handlingFollow up to#42630The error handler should be able to report exceptionsarising from exceeding the PHP memory limit. Becauseof changes made to error handling, the previouslyconfigured value is no longer sufficiently large.A similar change was also done in Symfony a while ago,seesymfony/symfony#44327.I used the following artisan command to determine the amountof memory required for error handling, using a reporter thatsimply writes to a file:```php<?php declare(strict_types=1);namespace App\Console\Commands;use Illuminate\Console\Command;final class MeasureHandlerMemory extends Command{    protected $signature = 'measure-handler-memory';    private int $peak;    public function handle(): void    {        $this->peak = memory_get_peak_usage();        trigger_error('', E_USER_ERROR);    }    public function __destruct()    {        $used = memory_get_peak_usage() - $this->peak;        echo "error handling used: " . $used . "\n";        $before = memory_get_usage();        $times = 10240;        $reserve = str_repeat('x', $times);        $after = memory_get_usage() - $before;        echo 'repeat times ' . $times . ' reserves: ' . $after . "\n";        $ratio = $after / $times;        echo 'ratio between bytes and repeat: ' . $ratio . "\n";        echo 'minimum times to repeat: ' . $used / $ratio . "\n";    }}```* Free memory in HandleExceptions::handleShutdown()While validating the effectiveness of#42630in our application, I found that the call `$error = error_get_last()`causes a tiny bit of memory usage. Thus, I think it is betterto clear memory as soon as entering the handler.* Update HandleExceptions.phpCo-authored-by: Taylor Otwell <taylor@laravel.com>

* Increase reserved memory for error handlingFollow up tolaravel#42630The error handler should be able to report exceptionsarising from exceeding the PHP memory limit. Becauseof changes made to error handling, the previouslyconfigured value is no longer sufficiently large.A similar change was also done in Symfony a while ago,seesymfony/symfony#44327.I used the following artisan command to determine the amountof memory required for error handling, using a reporter thatsimply writes to a file:```php<?php declare(strict_types=1);namespace App\Console\Commands;use Illuminate\Console\Command;final class MeasureHandlerMemory extends Command{    protected $signature = 'measure-handler-memory';    private int $peak;    public function handle(): void    {        $this->peak = memory_get_peak_usage();        trigger_error('', E_USER_ERROR);    }    public function __destruct()    {        $used = memory_get_peak_usage() - $this->peak;        echo "error handling used: " . $used . "\n";        $before = memory_get_usage();        $times = 10240;        $reserve = str_repeat('x', $times);        $after = memory_get_usage() - $before;        echo 'repeat times ' . $times . ' reserves: ' . $after . "\n";        $ratio = $after / $times;        echo 'ratio between bytes and repeat: ' . $ratio . "\n";        echo 'minimum times to repeat: ' . $used / $ratio . "\n";    }}```* Free memory in HandleExceptions::handleShutdown()While validating the effectiveness oflaravel#42630in our application, I found that the call `$error = error_get_last()`causes a tiny bit of memory usage. Thus, I think it is betterto clear memory as soon as entering the handler.* Update HandleExceptions.phpCo-authored-by: Taylor Otwell <taylor@laravel.com>