Splitter have memory leak

[Stéphane]

We just update all use of our Kendo control to use "kendo.destroy(context)"

Combobox, datepicker don't show any leak now

But we see that splitter still have some leak.

In ajax we refresh some information in our page, and remove the splitter each time.

In debug we check that "kendo.destroy" was call before we remove the DIV that was made into splitter.

If we just remove the call to kendo.splitter we don't have leak.

Thanks

[Petur Subev]

Hello Stephane,

I tried to see if I am able to reproduce any memory leaks but to no avail.

http://jsbin.com/omiTaPI/2/edit


Here is a JsBin page that creates two splitters and destroys them multiple times. I do no see any problems with the memory. Check the profiling screencast below.

http://screencast.com/t/pThCYTtCb

Kind Regards,
Petur Subev
Telerik

[Stéphane]

Hi,

I used your test page and I saw the leak.

The leak is not really big in term of memory (bytes), but the number of elements in the DOM is increasing really fast.

I attached 2 files (capture from you're exemple)

• One that use kendo splitter and show that the number of elements in the DOM is always increasing
• One that don't use kendo splitter (just commented Kendo) and show that the number of elements in the DOM go up and down, but stay at the same level

 

[Stéphane]

I forgot to mention that  I was often clicking on "Collect Garbage" in Chrome browser.

I want to know the DOM element that can't be release by the Garbage collector (the leak)

[Petur Subev]

Hello Stéphane,

I have logged the issue into our internal system so the Dev team can investigate further the case.

Sadly since I was not able to see what exactly makes the DOM Node count grow in such way I cannot offer you fix or work-around.


I am sorry for any inconvenience caused. As a small sign of our appreciation for bringing this issue to our attention I have updated your telerik points.

Regards,
Petur Subev
Telerik