I am working on a moderately sized SPA which makes use of jQWidgets. We currently use a jqxDropDownButton, with jqxListBox for it’s content, however during testing a significant slow down is noticed after a period of use.
I’ve investigated the jqxDropDown button in isolation, and have come to the conclusion that this is one of the areas responsible for both the memory leak and hit to performance that we are seeing. See my test page below:
Having profiled this using Chrome, I can see that every time I Add and then Remove the jqxDropDownButton, the number of div elements and objects in memory increases, but never decreases.
Can someone take a look at this and confirm the issue? Also if there is a workaround or I should be doing this differently, please let me know.
I should add that I tried the same test with jqxButton, and saw no memory leak, and it was correctly being cleaned up.
Thanks in advance.
- This topic was modified 4 years, 6 months ago by DuaneC.
To make things easier, I’ve also created a jsFiddle here https://jsfiddle.net/ku3qof2x/
To see the leak, click the add and remove buttons, capturing the heap snapshot every time.
We do not see the number of DIV tags to increase after adding/removing the DropDownButton. However, in case we reproduce the reported behavior, we will create a work item for future jQWidgets update. Thank you for feedback!
Ok thanks Peter.
Is there anything I can do to confirm with you what I am seeing? Should I e-mail images if that would help?
Can you could advise if there might be a short term solution for this? Due to it’s impact I may have to consider removing this widget from our app, but I would prefer not to do this.
I have since learned that we have a platinum support package included with our license, so if you think I should follow up there instead, please let me know.
Thanks in advance.
You must be logged in to reply to this topic.