Instances of components seems to be kept in the memory when they contain a ejs-richtexteditor component. To reproduce Please see the attached movie and demo project.
Attachment: 20220314_memleak_syncfusion_markdowneditor_movie_15345913.zip
somehow the forum validation did not let me complete my report because of "forbidden URLs" (there was no URL in it...), so let's try to post it again:
Here are the steps to reproduce:
The only difference between Block 1 and Block 2 is that Block 1 contains a ejs-richtexteditor component.
Here's the Markup of the Demo:
<div class="content" role="main">
<button (click)="onToggle1()" >TOGGLE Block 1 {{isVisible1 ? 'OFF' : 'ON'}}</button>
<button (click)="onToggle2()" >TOGGLE Block 2 {{isVisible2 ? 'OFF' : 'ON'}}</button>
<hr/>
<p>Block 1 - {{isVisible1 ? 'ON' : 'OFF'}} - count: {{counter1}}</p>
<div *ngIf="isVisible1">
<dummy-component [counter]="counter1"></dummy-component>
<ejs-richtexteditor id='mdDefault' #mdDefault editorMode='Markdown' height='250px'>
</ejs-richtexteditor>
</div>
<hr/>
<p>Block 2 - {{isVisible2 ? 'ON' : 'OFF'}} - count: {{counter2}}</p>
<div *ngIf="isVisible2">
<dummy-component [counter]="counter2"></dummy-component>
</div>
And here's the code of the Demo:
@Component({
selector: 'app-root',
templateUrl: './app.component.html',
styleUrls: ['./app.component.css']
})
export class AppComponent {
public isVisible1 = false;
public counter1 = 0;
public isVisible2 = false;
public counter2 = 0;
public onToggle1() {
this.isVisible1 = !this.isVisible1;
if (this.isVisible1) {
this.counter1++;
}
}
public onToggle2() {
this.isVisible2 = !this.isVisible2;
if (this.isVisible2) {
this.counter2++;
}
}
}
We couldn't include the fix for the issue due to some complexity and it will be included with our upcoming patch release on 26th April 2022.
Hi Bernd,
Sorry for the inconvenience.
We have faced more complexity in fixing this problem and also need to ensure more cases based on this fix. So, we will include your fix in our upcoming Vol 2, 2022 release, which is scheduled to roll out at the end of June, 2022. We appreciate your patience until then.
Regards,
Buvana S
We are facing complexity in resolving the reported issue on our end. We will include the fix in the upcoming weekly patch release, which is expected to be rolled out on July 19, 2022.
We are glad to announce that our Essential Studio 2022 Volume 2 SP release v20.2.0.43 is rolled out and is available for download under the following link.
We have also included the fix for the reported issue "Memory leak issue with Rich Text Editor component" with our Vol 2 2022 SP release. So please upgrade your package to the latest to resolve the issue from your end.
We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you require any further assistance.
Regards,