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
Should that happen? I am asking because of the following comment lines:
// We will use just one change listener for all live queries.
// We need to keep track of how many queries are running.
// When the last live query finishes we will cancel the listener.
The text was updated successfully, but these errors were encountered:
The error is "console.error: "(node) warning: possible EventEmitter memory leak detected. %d listeners added. Use emitter.setMaxListeners() to increase limit."
it's throwing that error on the _changeListener now. I'm not sure if this will improve performance (adding listeners on the changeListener instead of on the db) because I've not traced it's implications.
But, anyway, it's good to know that you can do a:
db._changeListener.setMaxListeners(30);
after you register your first finder to fix this. At least for now.
If you've added 11 listeners and the warning says 11 listeners added, that is normal. (Increase max listeners if you need more.) If you add 11 listeners and it says you have 100 listeners added, that is a memory leak.
Should that happen? I am asking because of the following comment lines:
The text was updated successfully, but these errors were encountered: