directive scope will not be destroy when call the remove method of splitter

[Freddy]

hello there,

 

I encounter a issue that, i have a directive in a pane of splitter, of course i can remove it and re-append it to the splitter. for now, the directive has a isolate scope, even though i had remove the current pane from the document, but the isolate scope is still there, is it makes the memory leak? because this operation maybe will be execute a lot time in a short time. so there will be a lot of scope objects in memory.

here is the demo in dojo

[Genady Sergeev]

Hi Freddy,

It is not recommended (some people even consider it bad practice) to remove directives with jQuery (or pure DOM operations) as this will surely lead to memory leaks.

It is best to remove elements using the angular way, for example ng-if. In case you really need to remove a directive with jQuery please consider calling manually $destroy on the scope.

In the specific case if your example though, ng-if seems to break splitter, whereas explicit $destroy leads to  JavaScript errors (please take a look at the sample). We will probably need to take deeper look in code. I will update the thread when we have resolution.

Regards,
Genady Sergeev
Telerik

 

 

[Genady Sergeev]

Hello Freddy,

Unfortunately at the moment there seems to be no way to remove panes and achieve 100% destroy on child scopes of removed panes. This is both a limitation of the splitter(which was not designed to be used in Angular environments) and quirks in the very angular framework. We will do our best to resolve the problem in the upcoming release.

Regards,
Genady Sergeev
Telerik