vueAABAcomparisondelta
vueAABAcomparisondelta
looking at these alone is not enough to determine whether there must be a memory leak problem. With regard to the situation in which you mentioned that snapshot will increase progressively, it may be because the project uses vuex, and every time you jump to the routing page, the data will be stored in vuex more or less. After jumping out of the current page, the data in vuex is still in memory, but this is not a memory leak problem. Because this data may have to be reused later on the routing page.
generally, memory leaks in the frontend generally occur in event registrations or some used but unreleased dom nodes. Check whether there is corresponding registration logic in the lifecycle of each component in the project, and it has not been released in the destoryed lifecycle function. This situation can be counted as a memory leak.
Previous: [muse-ui] when mu-tabs is switched, the loaded mu-data-table disappears for no reason.
Next: What should I do when Antd/Zent uses Popover in Table/Grid?