You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've implemented a Nuxt app utilizing vuex-search. The app is server-side rendered, and is experiencing a memory leak on the server. Loading any page (including pages that don't use the search function) increases the memory usage of the server until it eventually crashes.
By removing vuex-searchsearchPlugin from the 'plugins' section of of the store, the memory leak goes away. The searchPlugin settings are implemented just as in the example in the README (though of course for different state attributes).
Since this is occuring on loading of pages that don't have any custom implementation of vuex-search, and the only custom code that's written is the config that's passed to the searchPlugin method, it seems like the memory leak is probably something internal to vuex-search. I'll take a pass at the source code of this method and see if I can identify anything, but do you know of any implementations that use server side rendering with vuex-search that have successfully avoided this issue?
The text was updated successfully, but these errors were encountered:
I've implemented a Nuxt app utilizing vuex-search. The app is server-side rendered, and is experiencing a memory leak on the server. Loading any page (including pages that don't use the search function) increases the memory usage of the server until it eventually crashes.
By removing
vuex-search
searchPlugin
from the 'plugins' section of of the store, the memory leak goes away. The searchPlugin settings are implemented just as in the example in the README (though of course for different state attributes).Since this is occuring on loading of pages that don't have any custom implementation of vuex-search, and the only custom code that's written is the config that's passed to the
searchPlugin
method, it seems like the memory leak is probably something internal to vuex-search. I'll take a pass at the source code of this method and see if I can identify anything, but do you know of any implementations that use server side rendering with vuex-search that have successfully avoided this issue?The text was updated successfully, but these errors were encountered: