Update IdentityModel dependency

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I would like to configure the OpenIdConnectOptions for each request. As the OpenIdConnectHandler requires an IOptionsMonitor (singleton), I registered the services as scoped like this:

var builder = WebApplication.CreateBuilder(args);
builder.Services.AddScoped<IOptionsMonitor<OpenIdConnectOptions>, OptionsMonitor<OpenIdConnectOptions>>();
builder.Services.AddScoped<IOptionsMonitorCache<OpenIdConnectOptions>, OptionsCache<OpenIdConnectOptions>>();

It seems from .NET 6, this way of doing things causes a memory leak (the memory keeps growing):

For my test, I simply inject an instance of IOptionsMonitor<OpenIdConnectOptions> into a controller and run a bench (a few hundred requests)

.NET 5 results (same test):

It seems also that the issue only concerns OpenIdConnectOptions (but maybe not) because I tried with a custom options class and I didn’t notice any issue.

Expected Behavior

Same behavior as .NET 5

Steps To Reproduce

The repo to reproduce the issue: https://github.com/ylabade/options-memory-leak

Exceptions (if any)

No response

.NET Version

6.0.101

Anything else?

No response

[Tratcher]

The good news is that updating the dependency in AspNetCore servicing isn’t required, customers can update the IdentityModel dependency locally.

[Tratcher]

@sebastienros IdentityModel doesn’t have a good track record with breaking changes, we’d definitely want to test this in 7.0 first.