EasyXploit / HelpBot

A Discord bot designed for automated community moderation, leveling, chat utilities and much more!
MIT License
7 stars 1 forks source link

Crash due to maximum call stack size exceeded #84

Closed EasyXploit closed 2 years ago

EasyXploit commented 2 years ago

Describe the bug The bot crashes for unknown reasons due to a memory leak.

Error trace

(node:106078) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [ReadStream]. Use emitter.setMaxListeners() to increase limit
(node:106078) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 data listeners added to [ReadStream]. Use emitter.setMaxListeners() to increase limit
node:events:484
EventEmitter.prototype.emit = function emit(type, ...args) {
                                           ^
RangeError: Maximum call stack size exceeded
    at DelayedStream.emit (node:events:484:44)
    at DelayedStream._handleEmit (/home/dperales555/HelpBot/node_modules/delayed-stream/lib/delayed_stream.js:82:15)
    at source.emit (/home/dperales555/HelpBot/node_modules/delayed-stream/lib/delayed_stream.js:29:19)
    at source.emit (/home/dperales555/HelpBot/node_modules/delayed-stream/lib/delayed_stream.js:30:21)
    at source.emit (/home/dperales555/HelpBot/node_modules/delayed-stream/lib/delayed_stream.js:30:21)
    at source.emit (/home/dperales555/HelpBot/node_modules/delayed-stream/lib/delayed_stream.js:30:21)
    at source.emit (/home/dperales555/HelpBot/node_modules/delayed-stream/lib/delayed_stream.js:30:21)
    at source.emit (/home/dperales555/HelpBot/node_modules/delayed-stream/lib/delayed_stream.js:30:21)
    at source.emit (/home/dperales555/HelpBot/node_modules/delayed-stream/lib/delayed_stream.js:30:21)
    at source.emit (/home/dperales555/HelpBot/node_modules/delayed-stream/lib/delayed_stream.js:30:21)

Node.js v18.4.0
EasyXploit commented 2 years ago

The error has not reappeared in two months of consecutive monitored use, and it has not been able to be reproduced, so this issue will be closed, and reopened if this situation occurs again.