3urobeat / steam-comment-service-bot

📡 The most advanced Steam Account Manager Bot with mass coordinated comments/likes/favs/follows and plugin support
https://steamcommunity.com/id/3urobeatscommentbot
GNU General Public License v3.0
274 stars 40 forks source link

MaxListenersExceededWarning: Possible EventEmitter memory leak detected #78

Closed DJMarkus1337 closed 3 years ago

DJMarkus1337 commented 3 years ago

image

DJMarkus1337 commented 3 years ago

(node:5184) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unhandledRejection listeners added to [process]. Use emitter.setMaxListeners() to increase limit (Use node --trace-warnings ... to show where the warning was created) (node:5184) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 uncaughtException listeners added to [process]. Use emitter.setMaxListeners() to increase limit

DJMarkus1337 commented 3 years ago

nice update

3urobeat commented 3 years ago

Hey, thanks for opening an issue!
I got that error two times too but ignored it for now as everything seems to work fine and thought that something else on my machine might have caused that. But I will definitely look into what might cause this error.

And thanks! :D

DJMarkus1337 commented 3 years ago

ok worked me im change folder src laset version to new version and off auto update

DJMarkus1337 commented 3 years ago

folder src fixed

DJMarkus1337 commented 3 years ago

https://github.com/HerrEurobeat/steam-comment-service-bot/commit/bfa87aec44811c62608f2b31f17a1e83062578bb

DJMarkus1337 commented 3 years ago

this get error ?

3urobeat commented 3 years ago

That just caused an error when trying to update because the updater couldn't check for active comment processes but has nothing to do with this issue

3urobeat commented 3 years ago

I'll leave this open until I have an idea what caused the error

3urobeat commented 3 years ago

I'm not 100% sure this fixed this issue but I'm very certain this should be fine. If this message should appear again anyone can feel free to reopen this issue or create a new one!