6 ms·

First thing I do on a new Windows setup is turn on "handles", "threads", "Commit size", "NP pool" columns in task manager details... If you want to see some re

First thing I do on a new Windows setup is turn on "handles", "threads", "Commit size", "NP pool" columns in task manager details... If you want to see some real offenders... have a quick look at Asus's "LightingService.exe" (the daemon that controls their rgb LED coloring suite). Gets up to 2m+ handles after a day or two of running on my system. The next biggest offender on my system? Their ez updater "EzUpdt.exe" at ~60,000 handles. Haven't bothered looking at it with process explorer/procmon yet, but I'm sure it's a quick fix.

Scene_Cast2 5y ago
In my experience, removing that software is tricky as well. There is OpenRGB (among others) that should be able to control lighting on multiple peripherals. And FanControl (among others) for fan curves.
- tgtweak 5y ago
  It's a shit-show also, with every vendor having their own solution and 0 interop. RGB addressing isn't rocket science I'm not sure why every app needs its own proprietary daemon to handle this - mercy on your soul if you have corsair + asus + gigabyte in your system as I do.
  - ziml77 5y ago
    I think it's because no one standardized on protocols for addressing RGB lighting on RAM, GPUs, and motherboards. We at least have those ARGB headers fairly standardized now, but wiring up even things that are slotted into the motherboard would suck (having just a few fans with those is already a mess). Also the manufacturers probably love it because it pushes people towards not mixing products from different companies.
ziml77 5y ago
I didn't even check the handles on LightingService. That shit got uninstalled fast after I saw it eating an entire CPU core and then some. I honestly didn't even want any lighting control software but all the RAM that had the speed and latency that I wanted were decorated with them so I needed software to set them to a static color. Thankfully I learned about OpenRGB.
- josteink 5y ago
  > Thankfully I learned about OpenRGB. Especially for Linux-users where official support may not be available for your RGB HW (mobo, RAM, whatever), OpenRGB is a godsend. And scriptable too, so I can disable all that crap at boot-time.

Scene_Cast2 5y ago

In my experience, removing that software is tricky as well. There is OpenRGB (among others) that should be able to control lighting on multiple peripherals. And FanControl (among others) for fan curves.

tgtweak 5y ago
It's a shit-show also, with every vendor having their own solution and 0 interop. RGB addressing isn't rocket science I'm not sure why every app needs its own proprietary daemon to handle this - mercy on your soul if you have corsair + asus + gigabyte in your system as I do.
- ziml77 5y ago
  I think it's because no one standardized on protocols for addressing RGB lighting on RAM, GPUs, and motherboards. We at least have those ARGB headers fairly standardized now, but wiring up even things that are slotted into the motherboard would suck (having just a few fans with those is already a mess). Also the manufacturers probably love it because it pushes people towards not mixing products from different companies.

ziml77 5y ago

I didn't even check the handles on LightingService. That shit got uninstalled fast after I saw it eating an entire CPU core and then some. I honestly didn't even want any lighting control software but all the RAM that had the speed and latency that I wanted were decorated with them so I needed software to set them to a static color. Thankfully I learned about OpenRGB.

josteink 5y ago
> Thankfully I learned about OpenRGB. Especially for Linux-users where official support may not be available for your RGB HW (mobo, RAM, whatever), OpenRGB is a godsend. And scriptable too, so I can disable all that crap at boot-time.