Hi there,
I'm with Martin, and was able to narrow the issue down a bit.
Our directive look somewhat like this:
{
"a":"SystemId",
"a@href":"WebAccessUrl",
"div.AssignedTo":"SystemAssignedTo",
"div.ActivationTime": function(args){
var posSpace =
args.context.MicrosoftVSTSCommonActivatedDate.indexOf(" ");
if(posSpace > 0){
return
args.context.MicrosoftVSTSCommonActivatedDate.substr(0,posSpace);
}
return args.context.MicrosoftVSTSCommonActivatedDate;
},
"div.DurationTime": function(args){
var posSpace = args.context.MicrosoftVSTSCommonActivatedDate.length;
if(posSpace == 19){
[heavy use of string and date operations here]
return " " + numberofDays + "d";
}
return "";
}
}
The template is just a table with some div's, and the json data is
just a bunch of string properties. Nothing fancy here.
The memory is leaked because of the two functions defined in the
directive. It seems like the use of string operations could be a
problem here, as other functions that don't use string operations,
don't cause leaks (or at least, no noticable leak)
I'm not much into JavaScript, but I could not find any issues
about .substring() itself causing memory leaks, thus we think there
might be an issue in the way pure handles these functions.
Hope this helps.
René