Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Memory leak

See original GitHub issue

Module versions (please complete the following information):

vue: 2.x
vue-i18n: 8.24.3

Reproduction Link https://github.com/PeterAlfredLee/vue_i18n_issue

To Reproduce

Clone the project
yarn && yarn serve
Click show and destroy button
Take memory snapshot, you can see there are more than one VueComponent

Expected behavior It should be just one VueComponent, because other VueComponent should be destroyed.

Additional context This issue is relate to #1151. After reverse #1151, everything works fine. Also, I can’t reproduce the leaking that #1044 describe.

conclusion I think we should reverse #1151. WDYT?

Issue Analytics

State:
Created 2 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

2reactions

kazuponcommented, Apr 28, 2021

@PeterAlfredLee Thanks for your many and usual contributions. ✨

Do you have any work around solutions?

For the memory leak, unfortunately, I don’t have a workaround idea at the moment due to the prototyping of intlify devtools and vue-i18n-next more improvements (e.g. more type safe). 😞

now, I’m going to revert #1151 to avoid the current memory leaks issue.

1reaction

kazuponcommented, Apr 23, 2021

@PeterAlfredLee Thank you for your reporting! Related issue https://github.com/kazupon/vue-i18n/issues/1190

We need to work around the memory leak in another way.