Closed jessicah closed 7 months ago
Thanks for raising this; closing as duplicate of https://github.com/serilog/serilog-sinks-periodicbatching/issues/76, until we figure out what project the issue is in.
I removed seq as a sink, and used async console sink instead, and the memory leak seems to have gone away.
Thanks for following up. It'd be great to get a few more details over on the other ticket regarding your testing conditions, just so we know whether there's something for us to chase down or not. Thanks again!
Initially filed at: https://github.com/serilog/serilog-sinks-periodicbatching/issues/76
Description Serilog appears to end up with unbounded memory usage, creating a large number of CancellationTokenSources and ValueTasks.
Reproduction Program.cs:
LoggingRateLimiter.cs:
Expected behavior Memory to remain fairly constant
Relevant package, tooling and runtime versions
Additional context CancellationTokenSource
ValueTask