heap size issue similar to https://issues.apache.org/jira/browse/IGNITE-8892

We are seeing memory issue like exact mentioned in below Jira ID
https://issues.apache.org/jira/browse/IGNITE-8892

Other Details ::
1. We use ignite-core-2.16.0.jar still this issue is seen.
2. ignite client is started in tomcat to connect to the server
ClientConfiguration cfg = new ClientConfiguration().setAddresses(addresses);
IgniteClient client = Ignition.startClient(cfg);
3. ignite server is loaded with 1M data using code like below
ClientCache cache = client.cache("cache-name");
for (Object object : arrayList) {
cache.put(UUID.randomUUID().toString(), object);
}
4. facing the heap size issue (of 8M records even if we have 1M records in cache) and tomcat crashes

Object will be our own objects which we send to the below Filter.
IgniteBiPredicate filter1 = new IgniteBiPredicate() {
@Override
public boolean apply(String k, Object obj) {
return .equals(obj.getVa........);
}
};

try (QueryCursor> qryCursor = cache.query(new ScanQuery<>(filter))) {
qryCursor.forEach(entry -> {
matchedList.add(entry.getValue());
});
}
after executing above code memory issue is seen.

Can somebody pls help on this issue ?

Start by reviewing the linked IGNITE-8892 report and reproducing the Ignite 2.16.0 client setup in Tomcat with the shown cache.put loop and ScanQuery filter. Compare heap usage before and after collecting matchedList entries, and consider the issue done only when the cause of the excess heap growth and Tomcat crash is isolated.

Written by the indexing model from the issue text.