"Close All" sometimes results in runaway memory consumption

[Fusty]

I noticed this while trying out the application today.

To recreate all I have to do is click "Show History" and then "Close All". It leads to runaway memory consumption (on my system the tab dies after 9gb). Not sure what is causing it as I've only just started playing with this application.

I'll keep poking around as I have time and try to understand what is occurring.

I'm on Ubuntu 16.04 and I'm running this in Chrome version 59.0.3071.115

[talex5]

That's strange. I tried opening http://roscidus.com/blog/cuekeeper/ in Chrome 61.0.3163.100, clicking "Show history" and then "Close all" and I didn't see any extra memory being used (it was stable at about 123 MB). How long did it take you to notice it? Does it happen for you if you try the same thing in Firefox?

[Fusty]

I cannot recreate this in firefox. I'll export the data I have into the firefox instance tonight and test again.

In the meantime I made a GIF of this in action. The first time I hit close all it doesn't do it, but the second time it does. You can see the memory increases consistently.

Gif/Video

[talex5]

BTW, I never got around to writing the import feature - sorry! The only way to import currently is to recompile CueKeeper with the exported data as the default state.

(or maybe it's possible to export and import the IndexedDB database in a browser-neutral format... I haven't checked recently)

[Fusty]

That's fine, if I can't figure that out I can't really recreate this scenario and all is moot.