OOM Exception in v5 - InMemoryBackingStore

[torbenpedersen]

After conversion from v4 to v5, I'm observing OOM exceptions tied to the InMemoryBackingStore. Are there any options for reducing the in-memory size or replacing with a disk-based store?

UPDATE: the memory growth is occurring when pulling in chunks of messages from a specific folder - ...MailFolders.WithUrl(messages.OdataNextLink).GetAsync()
The request configuration is filtered to select a few attributes, such as ID and extended properties. In profiling the differences between v4 and v5 of the SDK but otherwise same logic, v4 reached 1.2 GB Private Bytes and v5 reached 5.1 GB. I will need to refactor the logic but if anyone has an idea on how to reduce the 4X memory increase, that would be appreciated!

System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.Collections.Generic.Dictionary`2.System.Collections.IEnumerable.GetEnumerator()
   at System.Linq.Enumerable.OfTypeIterator[TResult](IEnumerable source)+MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at Microsoft.Kiota.Abstractions.Store.InMemoryBackingStore.EnsureCollectionPropertyIsConsistent(String key, Object storeItem)
   at Microsoft.Kiota.Abstractions.Store.InMemoryBackingStore.set_InitializationCompleted(Boolean value)
   at Microsoft.Kiota.Abstractions.Store.InMemoryBackingStore.<>c__DisplayClass8_0`1.<Set>b__0(IBackedModel model)
   at System.Collections.Generic.List`1.ForEach(Action`1 action)
   at Microsoft.Kiota.Abstractions.Store.InMemoryBackingStore.Set[T](String key, T value)
   at Microsoft.Graph.Models.Message.set_SingleValueExtendedProperties(List`1 value)
   at Microsoft.Graph.Models.Message.<GetFieldDeserializers>b__92_25(IParseNode n)
   at Microsoft.Kiota.Serialization.Json.JsonParseNode.AssignFieldValues[T](T item)
   at Microsoft.Kiota.Serialization.Json.JsonParseNode.GetObjectValue[T](ParsableFactory`1 factory)
   at Microsoft.Kiota.Serialization.Json.JsonParseNode.GetCollectionOfObjectValues[T](ParsableFactory`1 factory)+MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at Microsoft.Graph.Models.MessageCollectionResponse.<GetFieldDeserializers>b__4_0(IParseNode n)
   at Microsoft.Kiota.Serialization.Json.JsonParseNode.AssignFieldValues[T](T item)
   at Microsoft.Kiota.Serialization.Json.JsonParseNode.GetObjectValue[T](ParsableFactory`1 factory)
   at Microsoft.Kiota.Http.HttpClientLibrary.HttpClientRequestAdapter.SendAsync[ModelType](RequestInformation requestInfo, ParsableFactory`1 factory, Dictionary`2 errorMapping, CancellationToken cancellationToken)
   at Microsoft.Kiota.Http.HttpClientLibrary.HttpClientRequestAdapter.SendAsync[ModelType](RequestInformation requestInfo, ParsableFactory`1 factory, Dictionary`2 errorMapping, CancellationToken cancellationToken)
   at Microsoft.Graph.Users.Item.Messages.MessagesRequestBuilder.GetAsync(Action`1 requestConfiguration, CancellationToken cancellationToken)

[andrueastman]

@torbenpedersen Any chance you can confirm the v5 version you are using?

[torbenpedersen]

v5.40 - I was able to work around it by processing 1 page at a time whereas in v4 the memory was high but manageable by getting all folder messages.

[sherlock1982]

I'm using V5 as well.
In the example I was gonna read the users from Azure:

        var userResponse = await client.Users.GetAsync(requestConfiguration =>
        {
            requestConfiguration.QueryParameters.Top = 500;
            requestConfiguration.QueryParameters.Select = ["accountEnabled", "givenname", "surname", "mail", "mobilePhone", "userType", "displayName", "userPrincipalName", "Id", "assignedPlans", "mail", "BusinessPhones"];
            requestConfiguration.QueryParameters.Filter = "userType eq 'Member'";
        }, cancellationToken: token);

        if (userResponse != null)
        await PageIterator<User, UserCollectionResponse>.CreatePageIterator(client, userResponse, (user) => {
                ordinaryUsers.Add(new AzureDirectoryUser(user));
                return true;
        }).IterateAsync(token);

A customer has >70K users. AzureDirectoryUser doesn't hold a reference to user. The memory usage is around 3Gb and OOM.
I see on top lots of things related to InMemoryBackingStore:

7f73ea702588 152 617,952 Microsoft.Graph.Models.User[]
7f73ea6b2410 3 1,081,416 Integration.Microsoft365.Storing.AzureDirectoryUser[]
7f73e3cbf560 28,896 1,625,232 System.String[]
7f73ea6b9548 74,000 1,776,000 Microsoft.Graph.Models.User
7f73e3b6caf8 74,012 1,776,288 System.Boolean
7f73ea705318 77,500 2,480,000 System.Collections.Generic.List<Microsoft.Graph.Models.AssignedPlan>
7f73e3d7bf30 77,644 2,484,608 System.Collections.Generic.List<System.String>
7f73ea706280 65,400 3,139,200 Microsoft.Kiota.Abstractions.Store.InMemoryBackingStore+<>c__DisplayClass8_0<System.Collections.Generic.List<Microsoft.Graph.Models.AssignedPlan>>
7f73e9d5b810 65,549 4,195,136 System.Action<System.String, System.Object, System.Object>
7f73e9cab378 77,172 8,025,888 Integration.Microsoft365.Storing.AzureDirectoryUser
7f73ea7057e0 65,401 26,410,840 Microsoft.Graph.Models.AssignedPlan[]
7f73e43ef988 5,049 45,483,827 System.Byte[]
7f73ea704d30 2,119,329 50,863,896 Microsoft.Graph.Models.AssignedPlan
56369f83aed0 755,435 61,620,136 Free
7f73e5b033f0 2,119,333 67,818,656 System.DateTimeOffset
7f73e3d715c8 2,119,336 67,818,752 System.Guid
7f73e9d5af78 2,193,479 70,191,328 System.Collections.Concurrent.ConcurrentDictionary<System.String, System.Tuple<System.Boolean, System.Object>>
7f73e9d5b8f0 2,193,479 70,191,328 System.Collections.Concurrent.ConcurrentDictionary<System.String, System.Action<System.String, System.Object, System.Object>>
7f73e9d5e6b8 2,341,630 74,932,160 System.Tuple<System.Collections.ICollection, System.Int32>
7f73e9d5a920 2,193,479 87,739,160 Microsoft.Kiota.Abstractions.Store.InMemoryBackingStore
7f73ea67b7d0 2,193,330 105,279,840 System.Collections.Concurrent.ConcurrentDictionary<System.String, System.Action<System.String, System.Object, System.Object>>+Node
7f73e3b65ac8 4,387,766 105,306,384 System.Object
7f73e9d5c590 2,193,479 122,834,824 System.Collections.Concurrent.ConcurrentDictionary<System.String, System.Action<System.String, System.Object, System.Object>>+Tables
7f73e9d5c260 2,193,479 122,834,824 System.Collections.Concurrent.ConcurrentDictionary<System.String, System.Tuple<System.Boolean, System.Object>>+Tables
7f73e3c189e0 4,392,530 140,809,232 System.Int32[]
7f73e3cb3598 2,193,924 175,513,920 System.Collections.Generic.Dictionary<System.String, System.Object>
7f73e3b6bf60 4,388,080 176,070,648 System.Object[]
7f73e3c1d7c8 4,861,833 216,487,014 System.String
7f73e9d5ae18 11,484,990 367,519,680 System.Tuple<System.Boolean, System.Object>
7f73e9d5fad8 11,474,675 550,784,400 System.Collections.Concurrent.ConcurrentDictionary<System.String, System.Tuple<System.Boolean, System.Object>>+Node
7f73e9d5c0e0 2,193,479 701,913,280 System.Collections.Concurrent.ConcurrentDictionary<System.String, System.Tuple<System.Boolean, System.Object>>+VolatileNode[]
7f73e9d5c410 2,193,479 701,913,280 System.Collections.Concurrent.ConcurrentDictionary<System.String, System.Action<System.String, System.Object, System.Object>>+VolatileNode[]

Since I don't really need it can i somehow replace it with a simpler version? No ConcurrentDictionaries etc?

I create client like this:

    public GraphServiceClient CreateClient()
    {
        return new GraphServiceClient(httpClientFactory.CreateClient(),
            new BaseBearerTokenAuthenticationProvider(new TokenProvider(tokenManager)));
    }

I don't need change tracking anywhere as I'm only reading. Can I disable the backing store completely?

[andrueastman]

Hey @torbenpedersen, @sherlock1982,

We've had a number of improvements in this area that will hopefully resolve this for you. In case this is still an issue, please raise a fresh issue at https://github.com/microsoft/kiota-dotnet

Improvements include

• Only track changed values when it matters microsoft/kiota-dotnet#368
• Improving serialization microsoft/kiota-dotnet#311
• fix: performance issue with the backing store microsoft/kiota-dotnet#326