After using the "ejs-multiselect" control, the page will not be destroyed.

[techlandandyzhang]

https://stackblitz.com/edit/stackblitz-starters-aknhns

I wrote a demo example. One dialog uses the ejs-multiselect, and the other dialog uses the ejs-dropdownlist. The dialog using ejs-multiselect does not get destroyed.

Note: Recording a snapshot requires selecting the corresponding URL:

Steps for the ejs-multiselect example:

1. After refreshing the page, click on Page 1 and record a snapshot.
2. Click "Open Dialog," and after 3 seconds, the dialog will automatically disappear. Then switch to Page 2 and record a second snapshot.

 

3. Compare the two snapshots, and you will find that the DialogPage is still present.

Steps for the ejs-dropdownlist example:

1. After refreshing the page, click on Page 2 and record a snapshot.
2. Click "Open Dialog2," and after 3 seconds, the dialog will automatically disappear. Then switch to Page 1 and record a second snapshot.
3. Compare the two snapshots, and you will find that the DialogPage does not exist.

[techlandandyzhang]

Do you have any results yet? Can you try some problems?

[Yohapuja Selvakumaran]

Hi andyzhang,

We have considered the reported issue "The MultiSelect Element Page is Not Destroyed Properly After Switching to Another Page" as a bug from our end, and the fix for the issue will be included in our upcoming first weekly release after Volume 3 release which is expected to be schedule on end of September.

You can now track the status of the feedback through the below link,

Feedback: https://www.syncfusion.com/feedback/61024/after-navigating-to-another-page-the-multiselect-elements-are-not-destroyed

Disclaimer: “Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization.”

Regards,

Yohapuja S

[Kokila Poovendran]

Hi andyzhang,

We have conducted a thorough validation of the issue that has been reported. Upon investigation, we found that in order to effectively address the memory leak problem that arises when attempting to switch between pages, it is necessary to invoke the destroy method of the multiselect component at the sample level. Please find the code snippet and sample below.

Code snippet:

Sample - https://stackblitz.com/edit/stackblitz-starters-5reral?file=src%2Fapp%2Fdialog.page.ts,src%2Fapp%2Fpage1%2Fpage1.ts,src%2Fapp%2Fpage2%2Fpage2.ts,src%2Fapp%2Fdialog2.page.ts

[techlandandyzhang]

Hi  Kokila

"The issue is not resolved; even with the addition of destroy() in ejs-multiselect, it cannot be destroyed. 

Page1 uses ejs-multiselect, which causes the Dialog not to be destroyed. 

Page2 uses ejs-dropdownlist, which can be destroyed."

[Kokila Poovendran]

Hi techlandandyzhang,

We have considered the reported issue "The MultiSelect Element Page is Not Destroyed Properly After Switching to Another Page" as a bug from our end, and the fix for the issue will be included in our upcoming upcoming patch release, which is expected to be rolled out in mid-October.

You can now track the status of the feedback through the below link,

Feedback: https://www.syncfusion.com/feedback/61024/after-navigating-to-another-page-the-multiselect-elements-are-not-destroyed

Disclaimer: “Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization.”

[Kokila Poovendran]

Hi techlandandyzhang,

We have included the fix for the issue "The MultiSelect Element Page is Not Destroyed Properly After Switching to Another Pag" with our package version “27.1.53”. Therefore, we recommend upgrading to our latest version to resolve the current issue.

Root cause

The rendered popup object not destroyed properly.

Release Notes: https://ej2.syncfusion.com/angular/documentation/release-notes/27.1.53?type=all#bug-fixes-14

[techlandandyzhang]

I have taken the latest version 28.1.37, but the issue still persists.

[Priyanka Karthikeyan]

 Hi techlandandyzhang,

 

We have investigated the reported issue, "The MultiSelect Element Page is Not Destroyed Properly After Switching to Another Page," using the previously shared sample in the mentioned version (28.1.37). Based on our testing, the element is not maintained as described. For your reference, we have provided a sample and a video illustration:

 

Sample: https://stackblitz.com/edit/stackblitz-starters-pvlhbjnk?file=package.json

 

To assist you further, we kindly request that you share a sample application where the issue is reproducible, along with detailed steps to replicate the behavior. This will help us analyze the problem more effectively and provide you with a prompt and accurate solution.

 

We appreciate your cooperation and are committed to resolving this for you as quickly as possible.

 

Regards,

Priyanka K