Closed pauldotknopf closed 8 years ago
That points to the underlying history library, not something within the router. I would open an issue there and test against the latest version to be sure.
I don't think that is the case. I replaced the browser history with the "in-memory" history, and same result.
Here is more info.
Using the example "sidebar", I added this code to test the memory leak.
After about 3 minutes of running, my heap size has grown 1MB.
I have ran a very similar test using
router5-react
and the heap size stayed stable.