Lots of memory still retained after renderer.destroy() called

[zachmullen]

Several hundred MB of data is still in my heap even after the renderer3D is destroyed, which leads me to believe the visualized DICOM data itself is being held onto somewhere. Is this a known issue?

[mohanishgupta]

I'm also facing a similar problem while working with minified xtk.js/xtk_edge.js . So I switched to the developmental set-up and it solved the problem for now. But I need this working with the minified files also. Pardon me if I'm missing something.
I've posted the question on SO: http://stackoverflow.com/questions/32094100/xtk-memory-issue-with-minified-xtk-edge-js-and-xtk-js-files