Hi Francois,
I found myself running into this issue too, took a long time staring at Chrome’s profiler to work out. For me, the problem was a mouseup event handler that jqxGrid adds to the parent document. This handler keeps essentially the entire grid in closure and is never removed (even with the destroy method).
Unfortunately I’m not sure of any way to avoid this problem without adding a handler removal in jqxGrid, moving the grid out of the iframe or reloading the parent page. Hopefully a fix will make it into a future release…
Cheers,
Andy
