ASUS Web Framework skyrockets RAM while playing Marvel Rivals!

[Feenix]

My issue is some sort of weird. Im running on 32GB of RAM and we all know some games to take plenty of space espacially the most newer ones like Rivals. Since my PC has a Mainboard made by ASUS and the GPU aswell I have Armory Crate installed and the services its coming with. Here is the issue I dont know since when it is a thing but either through the lates WIndows Updates or the latest Rivals Patch the Process ASUS NodeJS Web Framework starts to use 5GB of RAM while playing Rivals and that only while playing Rivals. It temporarily works to end the process since it automatically gets restarted anyways but its going back to it's normal usage of 14 MB up to 250 MB of RAM not sure where the depencies are. But after a couple of Minutes it also skyrockets again up to 5GB which almost fills my whole RAM and RIvals itself does take 11GB while playing aswell. If I dont do anything about it the Game crashes after almost every 2 hours and comes of with a GPU crash log. Since I locked a little into it, it seems related to the RAM usage which causes the crashes thanks to ASUS. Does maybe anyone have the same issue or any type of solution for it?

[plotch]

I would generally uninstall armory crate or anything related to ASUS in terms of software.
One possible reason for the ram usage is that they are using process hooks in everything that you are running to track performance, this might be interfering with the anticheat causing buffer overflows (this is a common issue with netease anticheat / neacsafe for instance and has had a tendency to interfere with rtss and similar applications).

[Feenix]

Originally posted by plotch:

I would generally uninstall armory crate or anything related to ASUS in terms of software.
One possible reason for the ram usage is that they are using process hooks in everything that you are running to track performance, this might be interfering with the anticheat causing buffer overflows (this is a common issue with netease anticheat / neacsafe for instance and has had a tendency to interfere with rtss and similar applications).

The Thing is that it never has been an issue it either occured since it was forced to update to Windows 11 24H2 or Rivals itself since the Season 1.5 Launch

[plotch]

Originally posted by Feenix:

Originally posted by plotch:

I would generally uninstall armory crate or anything related to ASUS in terms of software.
One possible reason for the ram usage is that they are using process hooks in everything that you are running to track performance, this might be interfering with the anticheat causing buffer overflows (this is a common issue with netease anticheat / neacsafe for instance and has had a tendency to interfere with rtss and similar applications).

The Thing is that it never has been an issue it either occured since it was forced to update to Windows 11 24H2 or Rivals itself since the Season 1.5 Launch

I get that.. the problem is that i have had to work with nodeJS for various projects over the years.. it has a very bad issue of compounding returned strings that cause buffer overflows (e.g in the case of a garbled string).
This is entirely an issue on the developer end as you can negate this, most don't however... in the case of ASUS software they have a LOOOOONG history of being extremely poorly made.

Whatever change has been made either on netease end or on microsofts end (or both) are more than likely causing this issue... either way i still do not recommend you using armory crate or any other performance tracker that runs 24/7... it's entirely pointless and will only soak up resources.

[Feenix]

Originally posted by plotch:

Originally posted by Feenix:

The Thing is that it never has been an issue it either occured since it was forced to update to Windows 11 24H2 or Rivals itself since the Season 1.5 Launch

I get that.. the problem is that i have had to work with nodeJS for various projects over the years.. it has a very bad issue of compounding returned strings that cause buffer overflows (e.g in the case of a garbled string).
This is entirely an issue on the developer end as you can negate this, most don't however... in the case of ASUS software they have a LOOOOONG history of being extremely poorly made.

Whatever change has been made either on netease end or on microsofts end (or both) are more than likely causing this issue... either way i still do not recommend you using armory crate or any other performance tracker that runs 24/7... it's entirely pointless and will only soak up resources.

Is there anything that that happens by deleting armory crate? I‘ve read about it and it seems to come with functionalitys that are important to the PC ofc everything was through google search so i cant really tell if those are 100% true or if there is nothing i need to be scared of by removing it

[Kosmanen]

Having same issues. Deleting AC isn't really the solution for me because i need that software for mb updates and bios fan control and all that stuff.

[plotch]

Originally posted by Feenix:

Originally posted by plotch:

I get that.. the problem is that i have had to work with nodeJS for various projects over the years.. it has a very bad issue of compounding returned strings that cause buffer overflows (e.g in the case of a garbled string).
This is entirely an issue on the developer end as you can negate this, most don't however... in the case of ASUS software they have a LOOOOONG history of being extremely poorly made.

Whatever change has been made either on netease end or on microsofts end (or both) are more than likely causing this issue... either way i still do not recommend you using armory crate or any other performance tracker that runs 24/7... it's entirely pointless and will only soak up resources.

Is there anything that that happens by deleting armory crate? I‘ve read about it and it seems to come with functionalitys that are important to the PC ofc everything was through google search so i cant really tell if those are 100% true or if there is nothing i need to be scared of by removing it

Originally posted by Kosmanen:

Having same issues. Deleting AC isn't really the solution for me because i need that software for mb updates and bios fan control and all that stuff.

I think the more important thing to test here is if your issues are solved by turning off armory services first and see if that helps.
If this is the case you might not need to remove AC entirely and just disable it as a startup service until you need it to use it.

If you just want fan control you have alternatives like https://github.com/Rem0o/FanControl.Releases that do this for you.

All the updates are available on their website as well, so it's not a requirement to have AC installed.

But yeah, try turning off armory as a startup service and see what mileage you get out of it as it might just be their nodejs implementation that is a pain in the a** right now.

[Captain_Scar]

Originally posted by plotch:

Originally posted by Feenix:

Is there anything that that happens by deleting armory crate? I‘ve read about it and it seems to come with functionalitys that are important to the PC ofc everything was through google search so i cant really tell if those are 100% true or if there is nothing i need to be scared of by removing it

Originally posted by Kosmanen:

Having same issues. Deleting AC isn't really the solution for me because i need that software for mb updates and bios fan control and all that stuff.

I think the more important thing to test here is if your issues are solved by turning off armory services first and see if that helps.
If this is the case you might not need to remove AC entirely and just disable it as a startup service until you need it to use it.

If you just want fan control you have alternatives like https://github.com/Rem0o/FanControl.Releases that do this for you.

All the updates are available on their website as well, so it's not a requirement to have AC installed.

But yeah, try turning off armory as a startup service and see what mileage you get out of it as it might just be their nodejs implementation that is a pain in the a** right now.

But just to know, i went to see my startup services and AC wasn't in it. And it pisses me off a bit cuz every time i used it it lagged and took me a bit too much time to just update little pilots

[Cult Leader]

Originally posted by plotch:

Originally posted by Feenix:

The Thing is that it never has been an issue it either occured since it was forced to update to Windows 11 24H2 or Rivals itself since the Season 1.5 Launch

I get that.. the problem is that i have had to work with nodeJS for various projects over the years.. it has a very bad issue of compounding returned strings that cause buffer overflows (e.g in the case of a garbled string).
This is entirely an issue on the developer end as you can negate this, most don't however... in the case of ASUS software they have a LOOOOONG history of being extremely poorly made.

Whatever change has been made either on netease end or on microsofts end (or both) are more than likely causing this issue... either way i still do not recommend you using armory crate or any other performance tracker that runs 24/7... it's entirely pointless and will only soak up resources.

Explain. Only being an A$$ because this is not true. I know first hand. I also would like to know of these projects you worked on... with distributed team? Net team? Devs? I am not going to lie, this has nothing to do with your issue. I am on the same win 11, I use Asus software and have the game fully updated. I do not have these issue. Please tell me why you stated this.

[BoomsticK]

uninstall all the bloatware on your poota dood

[plotch]

Originally posted by Cult Leader:

Originally posted by plotch:

I get that.. the problem is that i have had to work with nodeJS for various projects over the years.. it has a very bad issue of compounding returned strings that cause buffer overflows (e.g in the case of a garbled string).
This is entirely an issue on the developer end as you can negate this, most don't however... in the case of ASUS software they have a LOOOOONG history of being extremely poorly made.

Whatever change has been made either on netease end or on microsofts end (or both) are more than likely causing this issue... either way i still do not recommend you using armory crate or any other performance tracker that runs 24/7... it's entirely pointless and will only soak up resources.

Explain. Only being an A$$ because this is not true. I know first hand. I also would like to know of these projects you worked on... with distributed team? Net team? Devs? I am not going to lie, this has nothing to do with your issue. I am on the same win 11, I use Asus software and have the game fully updated. I do not have these issue. Please tell me why you stated this.

You say you aren't having this issue.. plenty of people are reporting that they are specific to armory.. you have several instances from 1-3+ years ago reporting the same problem so it's not even a rivals specific issue.

Who i have worked for is none of your business, and this is simply down to the way you addressed the question.

As for what i have done... i have written my fair share of rest API's for matchmaking and server management that heavily rely on memoryjs and child process stdio.. (special use case as the engine in use did not support custom websockets for API usage, thus we read memory)

I have run into plenty of instances of buffer overflow and memory leaks from the interplay between them and they all stemmed from string issues (in this case code assuming it is receiving sanitised json causing classes related to said strings to persist after the process has been killed, i.e the garbage collector fails to purge them for one reason or another)

This is also a fairly common problem that can be caused by simply writing to memory in a lot of cases, the reason why anticheats are relevant is because a lot of them both write and read memory. (which is why they are triggered by antivirus suites, as well as their attempts to prevent injections... it's quite literally why they need to be ring0)

But hey, don't take my word for it.. just go google nodejs and memory leaks and/or buffer overflow... this is a VERY common problem and they are more often than not directly related to strings and nodejs inability to garbage collect them, and them ultimately compounding over time.

You can go look up all the nodejs based cheats (also done via memoryjs)... they have the same problem when directly being targeted by an anticheat/antivirus process regardless of the nodejs/memoryjs instance being read-only or not.

If you are a nodejs developer i would hope you are at the very least aware of these issues.

[Feenix]

So by today they pushed out an update that removed the insane amount of RAM usage but ofc the Crashes still persist for some reason