-
-
Notifications
You must be signed in to change notification settings - Fork 539
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory Leak on publish #11245
Comments
When you say you can't publish on production anymore, what do you mean? The browser tab crashes, you get an error? Are you able to provide a video recording of what you're seeing? |
I'm sorry I was too vague. On publishing the php-fpm command starts using a lot of memory and after a few seconds all memory on my sever is used, php kills itself and the cms is down until I restart php. |
Do you have any event listeners? |
<?php
// app/Providers/EventServiceProvider.php
namespace App\Providers;
use Illuminate\Auth\Events\Registered;
use Illuminate\Auth\Listeners\SendEmailVerificationNotification;
use Illuminate\Foundation\Support\Providers\EventServiceProvider as ServiceProvider;
use Illuminate\Support\Facades\Event;
class EventServiceProvider extends ServiceProvider
{
/**
* The event listener mappings for the application.
*
* @var array<class-string, array<int, class-string>>
*/
protected $listen = [
Registered::class => [
SendEmailVerificationNotification::class,
],
];
/**
* Register any events for your application.
*
* @return void
*/
public function boot()
{
//
}
} And other Eventlisteners were not created. |
Bug description
I Upgraded from statamic 4 to 5 and after that I couldnt publish on production anymore. Weirdly it works on my local machine.
I am unsure how much influence it has, but I also have the revisions enabled.
How to reproduce
Sadly I don't know that. I am sorry, but maybe you can help me anyway.
Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
I use statamic headless, but I think that's of no importance.
The text was updated successfully, but these errors were encountered: