Hi Venkatesh,
This is the code requested.
function contextClickServerStorage(args) {
console.log('args ' + args.ID);
console.log('selected items ' + this.getSelectedRecords().length);
// remove repeated items
var result = _.uniq(this.getSelectedRecords(), 'Id');
console.log('cleaned selected items ' + result.length);
//console.log('details ' + JSON.stringify(result));
switch (args.ID) {
case "1"://Download
contextDownloadOption(result);
break;
case "2"://Check Group Security
contextGroupSecurityOption(result);
break;
case "3"://Maintenance View
contextMaintenanceViewOption(result);
break;
case "4"://Notify updated
contextNotificationViewOption(result);
break;
case "5"://Open file
contextOpenFileOption(result);
break;
}
}
function contextOpenServerStorage(args) {
if (!ej.isNullOrUndefined(rowIndex)) {
this.selectRows(rowIndex);
console.log(this.selectRows(rowIndex));
//this.getRowByIndex(rowIndex[0]).css("color", "red");
}
}
Unfortunately, it is not as simple as separate the code and creates an example for testing purposes. My current solution has around 20k lines.
I was wondering, why this call to contextOptions could generate the memory leak. I have another screen with similar code and different data and options. In that screen, the context works perfectly.
There is any way to active a debug log of Syncfusion libraries, so, I can follow up what is happening?
I fix it temporally with a work around adding custom toolbar icons and removing the call to customContext.
If you have more suggestions, please let me know.
Kind regards,
Juan