Memory Leak caused by MutationStore?

Intended outcome: My app requires a lot of mutations, making small updates to the DB continuously. Just a simple mutation:

         await client.mutate({
            mutation: gql`
               mutation {
                  ${gqlStatements.join('')}
               }
            `
         });

Actual outcome: Everything functions fine, but the memory heap fills up with mutationString’s that never seem to be collected.

How to reproduce the issue: Simply run a much of simple mutations and check the heap. Here’s a screenshop of Chrome Dev Tools: https://imgur.com/a/zPTKM

Version

• apollo-client@1.9.3

[joelclimbsthings]

Sure! Although I’m not really familiar with the react toolset, so I just mocked up a really simple vanilla JS example here: https://github.com/Dygerati/apollo-memory-leak

I’m using the pad here: https://launchpad.graphql.com/1xj5jr959

My github example will automatically create a heap snapshot in the directory every 10 minutes. After you let it run a bit, just load a couple snapshots into Chrome Dev Tools and set to compare. You should see a couple listings at the very top that are associated with Apollo–the one I sent a screenshot of earlier, as well as this one: https://imgur.com/a/zun8z

Thanks!

[dcosson]

Is this not just a memory leak by design? @hwillson what performance improvements are you referring to that would have solved this issue?

I haven’t been using Apollo for very long but the behavior I see in my app is that when using link state a record of every mutation gets inserted into the cache under the ROOT_MUTATION key and seem to stay there indefinitely. Is there some process that is supposed to periodically clear out old mutations?