Great question — answering as the UphillTech team:
It is definitely a memory leak but the app needs detailed profiling to zero down on the problem causing this. For your case, we can see the heap size grow but in order to know what exactly is causing the leaks or where the leaks are... you need to expand the identifiers and see which objects are still retained in memory(having a reference to the parent node that is your app) and which have lost a reference to the parent node. This will help you track down the pieces of your code(dom orJS) that are causing these memory leaks. There a bunch of good practices that can prevent your app from leaking that much... you can find some in this article (it is for angularjs but same concepts apply). I...
Full answer by Pato91: https://stackoverflow.stackexchange.com/a/49464387 (CC BY-SA 3.0).
Need it done for your business? UphillTech.
