Creating new sessions fails on node.js v22.7.0 with RangeError

[memendes123]

[2024-09-03 17:16:12] What's new: Fixed a lot of proxy related bugs, added a commentsIpCooldownPenalty setting, added events support to REST API plugin and made a few more QoL changes. Read the full changelog on GitHub.

[2024-09-03 17:16:12 | INFO] Logging in 478 account(s), where 0 qualify for fast login... Estimated wait time: 59.71 minutes
[2024-09-03 17:16:13 | WARN] [Main] RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: "length" is outside of buffer bounds while trying to get a new session for '03587688' using login credentials. Retrying login in 5 seconds...

[ERROR] [Main] Couldn't log in '03587ffs688' after 2 attempt(s). RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: "length" is outside of buffer bounds (undefined)

[ERROR] Aborting because the first bot account always needs to be logged in!
Please correct what caused the error and try again.

[3urobeat]

Hey, thanks for opening an issue!

Interesting error you've got there. I've done a quick look into my code and it seems like this error is caused inside the steam-session library, which was not written by me.

I will take a look at that library later, maybe I can narrow the issue further down.
I myself haven't encountered this issue before though, so it might be hard to replicate.

[3urobeat]

Which version of node.js are you using?

If you open output.txt the bot logs which version is used directly upon starting it, it's one of the first messages.

Apparently people are reporting this exact issue on node.js v22.7.0 in the protobufjs library, which steam-session uses.
Should you use v22.7.0, please downgrade and try again.
The node.js LTS (Long Term Support) version makes more sense for you anyway if you only want to run programs instead of developing as it is more stable.

[memendes123]

I was usong latest node and nom version. When i changed to node 18.5 and npm 10.5 this start work again Helder Alves 926725627 | ***@***.*** Rua do tanque nº 96 4820-664 Povoação, S.Gens Fafe 3urobeat ***@***.***> escreveu em qui., 5/09/2024 às 07:53 :

…

Which version of node.js are you using? If you open output.txt the bot logs which version is used directly upon starting it, it's one of the first messages. — Reply to this email directly, view it on GitHub <#261 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUDUWODY7UY5ELL33SC4ORTZU75VPAVCNFSM6AAAAABNSPUB6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZQG42DIMRRGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[3urobeat]

That's good to hear. Going to pin this issue for a while until this is patched so others can see it.