Memory leak

[Machine-Maker]

Version

nuxt-i18n: 6.18.0 nuxt: 2.14.12

Nuxt configuration

mode:

• [x] universal
• [ ] spa

Nuxt-i18n configuration

no configuration (aka whatever the defaults are)

Steps to reproduce

1. yarn create nuxt-app <name>

2. (settings used)

3. Added nuxt-i18n to buildModules in nuxt.config.js

4. yarn dev

5. Open whatever resource manager (task manager, system monitor, etc) and find the right node task

6. navigate to localhost:3000 and refresh a bunch and watch the memory go up.

Note: I tried it w/o vuetify and it doesn't happen, and it doesn't happen with just vuetify, only when both are present.

EDIT: Use this repo to reproduce it.

What is Expected?

node shouldn't run out of memory.

What is actually happening?

NodeJS crash

[Machine-Maker]

Ok, so it turns out that vuetify only speeds up the process significantly. I re-did the process w/o vuetify and added another page after project creation, then I just put location.reload() in the mounted() hook and let it run for a while, and the leak was still there.

[Br4x]

Same here

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[divine]

Hello,

Can't reproduce, also it's 404:

EDIT: Use this repo to reproduce it.

Thanks!

[leonardlin]

Update: It seems to happen in combination with vue-i18n in dev-mode. In prod-mode I can't reproduce it either. Still investigating, will report if I can reproduce again.

[leonardlin]

I need to retract my reproduction-post (deleted). It was only reproducible in dev-mode and not in prod-mode. I found the issue somewhere else.

[Machine-Maker]

Yeah, I knew it only happened in dev mode

[Abdulrahmanh995]

For me, the heap usage reduced by 50% when I just dropped those lines from nuxt.config.js.

    defaultLocale: 'ar',
    defaultDirection: 'rtl'