Hello,
Currently we're evaluating usage of kendo with angular 5.
I've noticed detached DOM trees when destroying the grids.
Please find attached 2 files:
1. Screencast of the snapshots as the creation/destroy progressing: https://ufile.io/20hfh
2. The app itself (without node modules, you can npm install to run it): https://ufile.io/0eone
Can you provide any input on this one? Is this a known issue or we're missing something?
Thank you
4 Answers, 1 is accepted
I've made some slight modifications to the test setup:
* Modified the app to add and remove grids one by one
* Used an allocation timeline to better visualize leaks
* Ran the app in production mode
The nodes that you spotted seem to be allocated only initially. Subsequent grids do not produce additional nodes, hence can't be qualified as a leak.
I can assume this is some sort of caching within the Angular framework.
Attached are the timeline, heap allocations and the modified project.
Regards,
T. Tsonev
Progress Telerik
Hi Rafal,
There is a known issue with memory leaks that is limited to development mode. Running the application in production mode should fix it. Also, upgrading your project to use the Ivy compiler should fix them for both development and production mode.
If the issue is not limited to development mode/pre-Ivy projects then please open a new bug report so we can investigate.
Best Regards,
T. Tsonev
Progress Telerik
Our thoughts here at Progress are with those affected by the outbreak.