The JS garbage collector releases memory at random times how long of a period are you testing over?
I would also suggest using the Chrome developer tools profile panel to check for leaks.
FYI when you take a heap snapshot in chrome dev tools it does initiate the garbage collector.
It would help expedite this issue if you put together a fiddle and verify that it reproduces this behavior.https://fiddle.sencha.com/#home