Jump to content


Doing trade offer poll since 1 (full update) - huge memory usage

node.js node-steam-tradeoffer-manager

  • Please log in to reply
2 replies to this topic

#1 neverhood


    Advanced Member

  • Member
  • PipPipPip
  • 56 posts

Posted 19 January 2019 - 05:50 PM

Hello, I'm using Steam card bot, but lately I got weird problem with memory usage.
Usually process using about 200MB RAM, but lately I got a lot of cards - about 100,000 and I did a lot of trades, my VPS is limited to 1GB memory, and my process going up to 1000MB+ and killing my VPS session.

Edited by neverhood, 22 January 2019 - 08:26 AM.

#2 Dr. McKay

Dr. McKay


  • Administrator
  • 2,187 posts

Posted 20 January 2019 - 12:25 AM

I'm sorry to say it, but if you don't want that behavior then you shouldn't be using steam-tradeoffer-manager. The entire purpose of the module is to keep stateful track of trade offers so that relevant events can be emitted when things change, but what you're asking for is to disregard old offers and only deal with new ones. That's not what steam-tradeoffer-manager is designed to do, and you'd probably be better off using some other library to deal with trade offers if your memory limitations require you to disregard older trade offers.

#3 neverhood


    Advanced Member

  • Member
  • PipPipPip
  • 56 posts

Posted 20 January 2019 - 05:31 AM

OK, Thank you for your response.

Also tagged with one or more of these keywords: node.js, node-steam-tradeoffer-manager

2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users