We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After our client runs for a couple of hours, when calling
db.get(xxx, function(...
we get:
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit. Trace at Db.EventEmitter.addListener (events.js:160:15) at Db.addEventListener.Db.on (/xx/node_modules/multilevel/lib/client.js:110:13) at Db.EventEmitter.once (events.js:185:8) at Db._queue (/xx/node_modules/multilevel/lib/client.js:209:13) at Db.db.(anonymous function) [as get] (/opt/xx/node_modules/multilevel/lib/client.js:173:10) [...]
thanks a lot.
PS: This is with multilevel running on the same box as the client, and the DB is on a local HDD.
The text was updated successfully, but these errors were encountered:
Can you tell me which event emitters you added on db? Multilevel itself only registers .on('open', fn).
db
.on('open', fn)
Sorry, something went wrong.
And you can catch those running db.on('error', function(err){ // your error handler })
db.on('error', function(err){ // your error handler })
No branches or pull requests
After our client runs for a couple of hours, when calling
we get:
thanks a lot.
PS: This is with multilevel running on the same box as the client, and the DB is on a local HDD.
The text was updated successfully, but these errors were encountered: