Mark Cilia Vincenti

@meinname please let me know. I've also updated to the latest version of the library with performance improvements.

Would you be so kind as to dumb it down into steps with screenshots to reproduce? And can you confirm that without the PR it does not give an issue?

That looks very helpful actually @meinname, thanks I'll look at it probably over the weekend.

@majiccode please let me know

@RichardBurns1982 @RolandoAvila the workaround is to pass on the created object as a parameter. For example changing: ```` builder.Services.AddSingleton(); ```` to: ```` builder.Services.AddSingleton(new AsyncKeyedLocker(o => { o.PoolSize = 20; o.PoolInitialFill...

@fabiocav gentle nudge :)

> Please add a description to the PR woth reasoning behind this change. done.

@crobibero ?

@crobibero Please let me know your intentions so I see whether or not to resolve the conflicts.

> Personally, I'm not sure I see the benefit. > > > offering superior performance and lower memory allocations > > The code paths that are now using your asynckeyedlock...