Skip to content
This repository has been archived by the owner on Dec 31, 2024. It is now read-only.

Out of stack space #745

Open
nadilas opened this issue Nov 27, 2019 · 2 comments
Open

Out of stack space #745

nadilas opened this issue Nov 27, 2019 · 2 comments
Labels
Status: Need More Info Lacks enough info to make progress Type: Performance Includes performance fixes

Comments

@nadilas
Copy link

nadilas commented Nov 27, 2019

hi there,

vue & vue-i18n version

Latest stable

Reproduction Link

Not yet available

Steps to reproduce

Build VueJs with remote localization repository and load all localization maps on startup. Roughly around ~140 key value entries for one localization.

What is Expected?

Normal operation.

What is actually happening?

Viewing the site in Microsoft Edge runs into “out of stack space” error with too many entries in the localization. Chrome handles any number of localization entries, well into the 7-800.

At first I thought it is an infinite loop as suggested by other sites, due to the translations being watched and reloaded on repository change. Reopening the site without edits and “watch” produced the same error. After deleting a few entries, the site reigns to normal and the error goes away. It clearly looks like a limit in the number of entries which can be used or an internal infinite loop within vue18n.

Any ideas?

@kimuraz
Copy link
Contributor

kimuraz commented Dec 4, 2019

@nadilas do you really need to load them all at once?
Maybe this could be an option for you: https://kazupon.github.io/vue-i18n/guide/lazy-loading.html

@nadilas
Copy link
Author

nadilas commented Dec 4, 2019

That is something which I currently have implemented via the vuex store, not that nicely though :)
Which solves the problem until one languages reaches a critical mass again, around the ~130 entries (already happened). And we would need to do further translations on the site. So yeah, it helped for a while, now the problem is back.

The one thing I can imagine is to break up the translations in the language based on the route, but that also only delays the inevitable.

@kazupon kazupon added Status: Need More Info Lacks enough info to make progress Type: Performance Includes performance fixes labels Feb 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Status: Need More Info Lacks enough info to make progress Type: Performance Includes performance fixes
Projects
None yet
Development

No branches or pull requests

3 participants