Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

large amount of com.microsoft.kiota.store.InMemoryBackingStore$Pair objects are allocated, memory leak?

Open
#2,235 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
api

Research direction

Start by reproducing the issue with the users/groups delta API in Java SDK 6.20.0 while persisting the models, then inspect the reported com.microsoft.kiota.store.InMemoryBackingStore$Pair allocations. Compare memory usage across repeated calls on the listed Java and OS configurations; done means the steady growth and excessive Pair retention are explained and resolved, with a regression check for the scenario.

Written by the indexing model from the issue text.

Description

Status: Needs Investigation type:bug
Describe the bug

trying to use the delta api and observed 10s of gigabytes of ram usage from this sdk.

Expected behavior

memory consumption should not be this large for a library doing http requests.

How to reproduce

just periodically call the users/groups delta api and try to persist the user/group models somewhere, you will see the ram usage steadily rising.

SDK Version

6.20.0

Latest version known to work for scenario above?

No response

Known Workarounds

none found atm.

Debug output
Click to expand log
Name,Live bytes,Live objects,Allocated objects,Generations
com.microsoft.kiota.store.InMemoryBackingStore$Pair	93,336,120 B (84.3%)	3,889,005 (81.4%)	15,340,787 (78.9%)	234

image

Configuration
  • OS: ubuntu, fedora
  • Arch: x64, aarch64
  • java: 21, 23
Other information

tried -XX:+UseG1GC without avail

Dominant language
Java
Stars
444
Forks
154
Avg merge
18h 28m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoftgraph/msgraph-sdk-java

All issues in microsoftgraph/msgraph-sdk-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.