SSR + vue-i18n starter kit issue (memory leak) about quasar-starter-kit

[rstoenescu]

Cannot reproduce. Can you tell me your exact Node version and OS (including its version) pls?
This has been tackled in the beta versions already.

Can you try with "@quasar/app" v3.1.0 which has updated Vue and Vue Router versions and tell if you can still reproduce it? If you can, then at this point it means that there's a high chance the culprit might be Vue itself.

[zknic]

Cannot reproduce. Can you tell me your exact Node version and OS (including its version) pls?
This has been tackled in the beta versions already.

Can you try with "@quasar/app" v3.1.0 which has updated Vue and Vue Router versions and tell if you can still reproduce it? If you can, then at this point it means that there's a high chance the culprit might be Vue itself.

Node: v14.16.1
OS: centos-release-7-4.1708.el7.centos.x86_64
kernel: 3.10.0-693.el7.x86_64

i have tried "@quasar/app" v3.1.0, it has the same problem. later i uesd "vue-cli" v4.5.13 to build a ssr project, the project has the same problem. (vue: 3.2.4, vue-router:4.0.11).it seems the culprit is Vue itself.

[zknic]

Cannot reproduce. Can you tell me your exact Node version and OS (including its version) pls?
This has been tackled in the beta versions already.
Can you try with "@quasar/app" v3.1.0 which has updated Vue and Vue Router versions and tell if you can still reproduce it? If you can, then at this point it means that there's a high chance the culprit might be Vue itself.

Node: v14.16.1
OS: centos-release-7-4.1708.el7.centos.x86_64
kernel: 3.10.0-693.el7.x86_64

i have tried "@quasar/app" v3.1.0, it has the same problem. later i uesd "vue-cli" v4.5.13 to build a ssr project, the project has the same problem. (vue: 3.2.4, vue-router:4.0.11).it seems the culprit is Vue itself.

The culprit should be vue-router. when i remove vue-router in vue-cli ssr project, the problem has been solved.

[rstoenescu]

Thank you for the reply.

In this case, can you open a ticket on the vuejs/vue-router-next repo pls? Also tag this ticket from there, so the other developers coming to Quasar can track this issue and its resolution.

Will close this ticket in the meantime, but will follow closely the vue-router one.

[zknic]

Thank you for the reply.

In this case, can you open a ticket on the vuejs/vue-router-next repo pls? Also tag this ticket from there, so the other developers coming to Quasar can track this issue and its resolution.

Will close this ticket in the meantime, but will follow closely the vue-router one.

sorry, i made a mistake. i did more test yesterday by using quasar framwork. when i create new project whitout i18n, the problem has been sovled.
vue-router's problem depends on which way you create the instance, quasar handled vue-router very well.

1.quasar create xxx
2.choose i18n
3.quasar mode add ssr
4.quasar dev -m ssr
5.use webbwnch to make a large number of requests

[zknic]

Modify as above, this can also prevent the server-side memory leak.

[rstoenescu]

Can you try putting the createI18n() inside of the default exported function pls and retest? (Also drop the other export)

[zknic]

Can you try putting the createI18n() inside of the default exported function pls and retest? (Also drop the other export)

you are right.

i tested these code, the project has the correct effect, no more memory leak.