Possible EventEmitter memory leak about ethereum-nft-sales-bot HOT 8 CLOSED

I noticed that FormData was consuming more memory than expected.
To address this, I removed the form-data package and switched to the native Node.js v18 FormData API in version 1.0.6.

As a result, the memory usage was reduced almost by half. Make sure you are now using Node.js version 18 or higher.

If you encounter any issues, please feel free to reach out.

from ethereum-nft-sales-bot.

Just noticed a new error in there:

Fontconfig error: Cannot load default config file: No such file: (null)

Adding a step to install fontconfig to dockerfile.

from ethereum-nft-sales-bot.

Nope, that wasn't it. Same errors around FormData.

from ethereum-nft-sales-bot.

Thanks for taking the time to report this issue.

I suspect it's because of the retry in your library, that tries to post the embed to discord multiple times.

Do you have duplicate discord notifications? retry only attempts to post if it has previously failed.

Also, as the readme states, fontconfig is a prerequisite. It is not an error.

I will look into the FormData warning.

from ethereum-nft-sales-bot.

Do you have duplicate discord notifications? retry only attempts to post if it has previously failed.

nope, it does not post anything to discord if ran on ecs. However, it does post to twitter when ran on ecs.

When ran locally, it posts both to discord and twitter.

from ethereum-nft-sales-bot.

updated the traceback with some more details. It starts off with event warnings, and then with a socket hang up after a while.

from ethereum-nft-sales-bot.

feel free to close this, I think it has something to do with ecs networking config...

I just tried this same bot on ec2 instances, and everything works fine.

from ethereum-nft-sales-bot.

Brilliant, thank you!

from ethereum-nft-sales-bot.