You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a setup with multiple nodes connected to relay. Usually on start works with no problems after 1 day or so of runtime. We usually experience this warning an all of the nodes and we see a spike of 100% cpu constant usage after that, which slows down dramatically other running processes. (I'm not sure those are related, but everything seems to happen after that warning log).
Also, we experienced that nodes lose pubsub messages after that as well.
It's the Dialer Relay that logs that warning.
Error:
(node:2880541) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 relay:removed listeners added to ReservationStore. Use ev ents.setMaxListeners() to increase limit
Steps to reproduce the error:
Relay Setup:
asyncfunctionmain(){constnode=awaitcreateLibp2p({peerId: awaitcreateFromJSON(rid),addresses: {listen: ['/ip4/127.0.0.1/tcp/5040/ws'],announce: ['/dns4/relay.smoothly.money/tcp/443/wss/']},transports: [webSockets(),],connectionEncryption: [noise()],streamMuxers: [yamux({maxMessageSize: 1<<20// 1 MB})],services: {identify: identifyService(),relay: circuitRelayServer({reservations: {defaultDataLimit: BigInt(1<<20),// the default maximum number of bytes that can be transferred over a relayed connection}}),pubsub: gossipsub({allowPublishToZeroPeers: true})},peerDiscovery: [pubsubPeerDiscovery({interval: 1000})]})console.log(`Node started with id ${node.peerId.toString()}`)console.log('Listening on:')node.getMultiaddrs().forEach((ma)=>console.log(ma.toString()))node.addEventListener('peer:discovery',async(evt)=>{const{ id }=evt.detail;console.log("Found:",id);awaitnode.dial(id);})}main()
Version:
"libp2p": "^0.45.9"
Platform:
Linux nf 6.2.0-26-generic Update libp2p-swarm to version 0.23.0 🚀 #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Subsystem:
Dialer
Severity:
Medium
Description:
I have a setup with multiple nodes connected to relay. Usually on start works with no problems after 1 day or so of runtime. We usually experience this warning an all of the nodes and we see a spike of 100% cpu constant usage after that, which slows down dramatically other running processes. (I'm not sure those are related, but everything seems to happen after that warning log).
Also, we experienced that nodes lose pubsub messages after that as well.
It's the Dialer Relay that logs that warning.
Error:
(node:2880541) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 relay:removed listeners added to ReservationStore. Use ev ents.setMaxListeners() to increase limit
Steps to reproduce the error:
Relay Setup:
Dialer Setup:
The text was updated successfully, but these errors were encountered: