Aaron Stannard

Just for clarification: this bug affects actors who use `IWithTimers` and call the `StartTimer` method inside the actor's `PreStart` override

I tried to reproduce this @brah-mcdude ```csharp async Task Main() { // Initialize Actor System var system = ActorSystem.Create("MySystem"); // Create Props for the EchoActor var props = Props.Create(); //...

> Terminate and/or CoordinatedShutdown a system in OOM situation. So I missed this - but this is largely an unhandleable situation and `CoordinatedShutdown` won't run correctly because processes are aborted...

See https://learn.microsoft.com/en-us/dotnet/api/system.outofmemoryexception?view=net-7.0 for a fuller explanation on what you can do to log this type of error (`Environment.FailFast`), but there are no tools to handle it once it gets going.

> but system.WhenTerminated should be completed even after an exception in system.Terminate() itself. The callbacks registered in System.RegisterOnTermination(StopApplication) could/should be executed even after an exception in CoordinatedShutdown Ok, that is...

Any updates on this @Zetanova ?

This is definitely a long-standing bug with Akka.IO - we're using a very sloppy technique for ensuring the mutual destruction of actors inside of here, hence the useless spam in...

I'm sorry, but we're going to need more details here - can you give us a timeline of what happened exactly? This sounds like a config and ops issue on...

> This is all configuration, sending data is very unstable, it is very easy to get this exception, and then the node will stop, I mainly use the cluster singleton...

Have you consider increasing your max frame size in Akka.Remote? It defaults to 128kb: ```hocon akka.remote.dot-netty.tcp.maximum-frame-size = 128000b ``` This error appears to be that one of the nodes is...