Nicholas Blumhardt

I'm not keen on dropping the dependencies here, not least because of the downstream breakage, but also because this creates one more barrier to adopting Serilog: the default .NET web...

Thanks for the report! Someone will need to set up "break on all exceptions", or step through the test in a debugger to narrow it down. I assembled a test...

Thanks @pikoscielniak; does "Break on all exceptions" show anything up?

Does the issue persist if you switch from `CreateBootstrapLogger()` to `CreateLogger()`?

@pikoscielniak thanks for helping to track it down. `CreateBootstrapLogger()` creates a `ReloadableLogger`, which the `UseSerilog()` callback reconfigures and then freezes. Freezing is a stateful operation: https://github.com/serilog/serilog-extensions-hosting/blob/dev/src/Serilog.Extensions.Hosting/Extensions/Hosting/ReloadableLogger.cs#L80 Not sure how best...

https://nblumhardt.com/2020/10/bootstrap-logger/#why-cant-we-just-do-both has some info on the problems `CreateBootstrapLogger()` resolves; if those issues don't apply to you then it's fine to just use `CreateLogger()` instead.

@span @MichaelDeutschCoding sounds like you're hitting something else; if you're sure it's Serilog-related, could you please post a new issue and include as much detail as possible? Thanks!

Thanks for the heads-up! This looks like it's due to `EventSourceLoggerProvider` holding on (permanently?) to all of the `EventSourceLogger`s that it creates: https://github.com/dotnet/runtime/blob/main/src/libraries/Microsoft.Extensions.Logging.EventSource/src/EventSourceLoggerProvider.cs#L36 I'm not sure why this design is...

Thanks @spolaore and @raphaabreu 👍 I think we'll want to take a similar approach to MEL, here. Yes, Serilog calls the other providers directly (it completely replaces `LoggerFactory` when enabled)....

@ivanmonteiro not sure what's going on in your case, but if you're load testing with a lot of concurrency, it could just be that `System.Console` can't keep up. First step...