Potential memory leak

[anjor]

I was trying to upload a directory about ~18G in size using w3up yesterday

cid: bafybeiet7ksjxjgze64ujy3373gipvz2rornpbx6qowhbudwhsmfik32uy

and got following warnings:

⠋ Storing 55%(node:34318) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 101 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit
⠙ Storing 55%(node:34318) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 101 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit
⠙ Storing 55%(node:34318) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 102 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit

[gobengo]

@anjor I believe @alanshaw fixed this with
storacha/w3up#1227
and released with @web3-storage/upload-client@12.3.2 storacha/w3up#1228

I believe if you npm install -g @web3-storage/w3cli, the semver ranges on that package will pull in this latest upload-client with the memory leak fix. I tried it out and see lower memory usage.

@anjor When you use latest upload-client with this fix, do you no longer see the Possible EventTarget memory leak detected?

[gobengo]

@anjor Testing on our side seems to indicate this is fixed. Please reopen the issue if you can reproduce the issue and we'll take another look!