Nuxt SSR has memory leak when feather-vuex is connected
See original GitHub issueSteps to reproduce
- Clone this https://github.com/DreaMinder/feathers-vuex-leak-reproduction, run
npm i
- Run
npm start
- Run 'npm load` in separate terminal (maybe multiple times)
- Watch for memory usage and terminal errors
Expected behavior
Stable memory usage
Actual behavior
- Terminal throws error
(node:10032) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 removed listeners added. Use emitter.setMaxListeners() to increase limit
- Memory usage increases under load and remains high while idle.
- When memory usage hits limit, process crashes.
System configuration
Tested on ubuntu\osx\windows. Both feathers-vuex 1.0 and 2.0.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Solving server-side memory leaks on Nuxt.js - Medium
Here's what we do now to test properly if we have memory leaks on a local server. To detect memory leaks, we use...
Read more >Nuxt | FeathersVuex
Preventing Memory Leaks. The default settings of Feathers-Vuex include having realtime events enabled by default. This will result in increased memory usage ...
Read more >Nuxt huge memory usage / leakage and how to prevent
I think it is time to share my understanding (even though it's little):. #1 as vue-router use prefetch there may be heavy memory...
Read more >Common memory leak issues in nuxt.js
Incorrect practices of using methods and data in vue files. Sometimes inner array operations might introduce an infinite loop too. If we have...
Read more >Any advice on finding a memory leak? Mode: SSR : r/Nuxt
7.1K subscribers in the Nuxt community. Nuxt is a JavaScript framework for creating Universal Vue.js Applications.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I had the same issue but is easly fixed with disallowing events on the server:
I was working on a documentation update but the latest version 2.3.1 broke somethings for me…
I’ve added this to the 3.0 docs. Will be shipping soon.