search

cs-discord-at-ucf / lion

🦁A Discord bot from scratch for the UCF Computer Science Discord.
MIT License
42 stars 18 forks source link

EventEmitter memory leak #324

Open c650 opened 3 years ago

c650 commented 3 years ago 
(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
c650 commented 3 years ago

picture issue actually caused by #314 and not a bug, but these logs still are a concern

tanndlin commented 3 years ago

Is this only new to the last deployment?

c650 commented 3 years ago

i am not sure because we dont have logs from the containers that ran before azure migration

tanndlin commented 3 years ago

Dont believe I've seen this in a week or more

suneettipirneni commented 3 years ago

This bug is caused by winston, from what I gather it happens when too many errors are being caught and logged by winston.