Bug: Another memory leak

[LlorxParticipant]

As I cannot edit my last post title anymore (http://www.jqwidgets.com/community/topic/bug-memory-leak-and-cannot-destroy-iframed-grids/) I create a new one.

Simply, when creating a jqxButton (which is created when creating a scrollbar and which is created when creating a grid) it attaches events to the window.top.document, but don’t clears them when destroying the button.

As I cannot show any fiddle because of the destroy bug on jsfiddle I talk on the other post, I simply tell you how to discover it. Call on the console “$._data(window.top.document, “events”).mouseup”, see the array length, then create a button, see the array increased, then destroy the button and see how the array decreased a bit, but not reaching the first length, so events are leaked.

[LlorxParticipant]

I fixed the bug by modifying the source code, as I needed to get this fixed ASAP, but EULA don’t allows me to post code here :-/

[HristoParticipant]

Hello Llorx,

Thank you for the interest.
We have a similar forum topic:
http://www.jqwidgets.com/community/topic/bug-memory-leak-and-cannot-destroy-iframed-grids

Best Regards,
Hristo Hristov

jQWidgets team
http://www.jqwidgets.com

[LlorxParticipant]

Of course you have a similar forum topic. Is my other post which I state in this post (Guess you didn’t read it :-() that I cannot modify the title with another different memory leak :-/

[Peter StoevKeymaster]

window.top.document attached event is removed on Grid destroy. At least in the current version.

[Author]

Posts