When analyzing our heaps on our server, the array mountedInstances gets larger and larger with each check, even with manually triggering garbage collection. This eventually takes up a LOT of memory.
We are currently using react-document-title within our isomorphic components, which in turn uses this library.
When we are on the server, it seems like we shouldn't need to keep track of mounted instances at all, right? Is that within the scope of this library to handle, or should we be accounting for this in our implementation?
Happy to help work on solution, just wanted to see if you think this is an issue with the library or not.
When analyzing our heaps on our server, the array
mountedInstances
gets larger and larger with each check, even with manually triggering garbage collection. This eventually takes up a LOT of memory.We are currently using
react-document-title
within our isomorphic components, which in turn uses this library.When we are on the server, it seems like we shouldn't need to keep track of mounted instances at all, right? Is that within the scope of this library to handle, or should we be accounting for this in our implementation?
Happy to help work on solution, just wanted to see if you think this is an issue with the library or not.