Sapphire - Imagine a Framework•16mo ago

Memory Leak

MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 interactionCreate listeners added to [Client]. Use emitter.setMaxListeners() to increase limit

I recently got this error, my bot only has 2 slash commands and 4 context menus, which are not used much, I already asked in the djs server and they said to go ask here instead

10 Replies

Lioness100•16mo ago

Could you show the stack trace?

-Carlos👑OP•16mo ago

I already rebooted the server so the errors were cleared, however it also displayed this: Error: Opening handshake has timed out

Lioness100•16mo ago

What's the stack trace for that

-Carlos👑OP•16mo ago

I already rebooted the server so the errors were cleared

Lioness100•16mo ago

Maybe you have too many awaitMessageComponent calls you didn't add a time property too for auto-clearing

-Carlos👑OP•16mo ago

none of my slashes or context menus uses that also i've been running slash commands and context menus for a while and I cannot replicate the error, could be a host issue?

Lioness100•16mo ago

I'm out of ideas without the code or the full error

-Carlos👑OP•16mo ago

if I ever get the error again I will create another post and if I remember correctly in the error there were a lot of Error: Opening handshake has timed out probably 10+

Bejasc•2mo ago

Hey @🠷Carlos👑, sorry to Necro, did you ever find the cause of this? I'm in a similar spot with one of my bots running now. Only had a handful of slash and context commands. It's been running fine in a production state for months. Opening handshake has timed out

Error: Opening handshake has timed out
    at ClientRequest.<anonymous> (/home/apps/sc-australis-bot/node_modules/ws/lib/websocket.js:873:7)
    at ClientRequest.emit (node:events:519:28)
    at TLSSocket.emitRequestTimeout (node:_http_client:845:9)
    at Object.onceWrapper (node:events:633:28)
    at TLSSocket.emit (node:events:519:28)
    at TLSSocket.Socket._onTimeout (node:net:590:8)
    at listOnTimeout (node:internal/timers:573:17)
    at processTimers (node:internal/timers:514:7)

Error: Opening handshake has timed out
    at ClientRequest.<anonymous> (/home/apps/sc-australis-bot/node_modules/ws/lib/websocket.js:873:7)
    at ClientRequest.emit (node:events:519:28)
    at TLSSocket.emitRequestTimeout (node:_http_client:845:9)
    at Object.onceWrapper (node:events:633:28)
    at TLSSocket.emit (node:events:519:28)
    at TLSSocket.Socket._onTimeout (node:net:590:8)
    at listOnTimeout (node:internal/timers:573:17)
    at processTimers (node:internal/timers:514:7)

Favna•2mo ago

This is not a memory leak. Nor is it an error. As the first word says, it's a warning. A 2 second google gives many results such as https://stackoverflow.com/questions/49946001/nodejs-maxlistenersexceededwarning. You either ignore it, or you set the max listeners to a higher count. As for the "Opening handshake has timed out", that is not Sapphire related and could be argued isn't even DiscordJS related. As the stracktrace shows, this is an error that comes from the ws (websocket) library and TL;DR just means the websocket fails to complete a handshake with Discord's servers. This could be a deeper networking issue on your server's end, an issue on Discord's end, or anything in between. Also, again there are many similar posts online: - https://stackoverflow.com/questions/61860024/connection-to-socket-gets-error-websocket-opening-handshake-timed-out-using-ja - https://github.com/websockets/ws/issues/1574 - https://github.com/discordjs/discord.js/issues/9571

Stack Overflow

Nodejs MaxListenersExceededWarning

I have an error and I don't know how to solve it. It happens only some times. Error message: (node:9140) MaxListenersExceededWarning: Possible EventEmitter memory leak detec ted. 11 error listeners

Stack Overflow

Connection to socket gets error "WebSocket opening handshake timed ...

About 4 hours of research...here we go. I have a C# program that sends and listens for anything coming in a specific Socket. Using the sockets, C# can send stuff to it and can receive from it just...

GitHub

handshakeTimeout error code · Issue #1574 · websockets/ws

[ X ] I've searched for any related issues and avoided creating a duplicate issue. Description I'm writing a Websocket client. When a connection fails I used to received the err.code ETIMED...

GitHub

Issues · discordjs/discord.js

A powerful JavaScript library for interacting with the Discord API - Issues · discordjs/discord.js

Gaming

Programming

Memory Leak

Did you find this page helpful?