Open jonoogle opened 8 years ago
Here is an example. I took the counties example, removed the tables, made the extension conditional on a variable hideShow and then made a button which flipflops hideShow. If you keep clicking on it memory usage increases but never comes down to original value.
We have an app which is "refreshing" every 10 seconds using another extension which just increments a Qlik variable at a regular interval (modified version of QvTicker - https://github.com/thomasfriebel/QvTicker). The effect is that objects are displayed conditionally based on the value of the variable giving the illusion of a slideshow presentation.
We noticed that after a full day some browsers were crashing. Investigating further we found that it is most likely due to memory usage. Isolating the problem we made a version of the map without any SVG objects and ran it concurrently with the app with the objects and no other charts. The result after 5 hours was that the app without any SVG maps was about 35MB (Chrome Task Manager measure) and was stable. The app with 4 SVG maps was 400MB and steadily increasing.
I love this extension. It is really well done and extremely useful. It would be nice if this issue could be addressed.