[francoisParticipant]

Hello Dimitar,

That the issue was iframe-related was my first guess, and I have spent some time trying to figure out a way to implement jqxGrid in an iframe (that can and will be reloaded) without success. I’ve done similar tests (loading libraries in the same iframe, and reloading them) without issues.

Could you provide an example of jqxGrid inside an iframe that will not leak if the iframe is reloaded?

I do believe it may be an issue with jqxGrid holding on to specific objects of jQuery. During my analysis, I did observe that the memory leak was much less important (3-4mb vs 15mb) if jQuery was not part of the iframe, but rather called from the parent of the iframe as seen below:

‘if(typeof $ === ‘undefined’) {
var $ = jQuery = window.parent.$;
jQuery = window.parent.jQuery;
}’

This however, can lead to unexpected behaviour of the code.

[francoisParticipant]

Hello Dimitar,

This has been verified in both Chrome 42 and IE11.

I believe this same issue occurs on your demos. Please see the attached screenshot of the growing memory. Every snapshot is taken after a right click -> reload frame.

The worst thing is that IE11 does not wipe local memory when you change window.location to another domain or hard reload (f5, ctrl+r), and carries that memory for a very long time.

[Author]

Posts