Alexander

@gbiryukov we are using this approach. Each request creates a new client instance and cache. Sorry if that wasn't clear from my previous messages.

@benjamn thanks for the quick update! We have tried the new version of `getMarkupFromTree` with `renderPromise.clear()` before `3.3.14` release (just copied function implementation with fixes) patched getDataFromTree.js file ```js import...

Was looking through the objects inside the heapdump, filtered objects by "Retained size" and found one strange thing, maybe this will help. Significant amount of space is reserved by ObservableQuery...

@benjamn @hwillson ok, I will double-check that. But, for sure I used patched version of getDataFromTree. Will let you know when I will have results with 3.3.14

Tried `3.3.14`, unfortunately it still leaks :crying_cat_face: Heapdumps: https://drive.google.com/file/d/17JIq8fkbfWaSzYKWaebDOjrHCQQRahr6/view?usp=sharing https://drive.google.com/file/d/1DUnZRqss2eE1mLg7iyKs14NcM9DGbjW5/view?usp=sharing

Hi @benjamn! Thanks for the update, going to test `@apollo/[email protected]` ASAP. As for the :wastebasket: button, we used `heapdump` package to collect heapdumps from kubernetes pods. Can't actually use devtools...

Hi @hwillson! Hadn't chance to check newer versions of the apollo client, going to check that this or next week, will inform you about the results ASAP

tried `3.4.10`, but unfortunately, we still have a memory leak in production...

Tried `fetchPolicy: no-cache` this one reduces memory and CPU consumption significantly, but memory leak is still present :cry: Currently, we have test setup with apollo3 with mirrored traffic from production,...

Looking forward to try `3.4.14`, hope this version will solve the issue! **UPD**: unfortunately that didn't help `3.4.15`. ```js client.cache.reset({ discardWatches: true }); ```