I launched Sysinternals DebugView today to do some debugging and was surprised to see the following:
Some service installed on my computer was pumping tons of messages to my computer's debug console, writing the same message several times a second: "GameScannerService(RzProcessManager) (0xb20) (0xcb4)." It didn't take long to figure out that this service is part of the Razer Comms package, which must have installed along with the default Razer Synapse applications that you're prompted to install when you plug a new Razer device into your computer. I don't even have any games installed on this computer, so I obviously don't need this service- but I've got a much bigger problem: This is a Windows logo-certified commercial product that's installed on literally millions of machines around the world that's pumping thousands and thousands of lines of useless information to the debug consoles of those computers all the time. That's a huge waste of collective CPU resources, and it's just plain terrible design. Release-build software shouldn't ever dump anything to the debug console, ever. How in the world did this get past Razer QA and Microsoft's certification labs?
Since I don't need the service, I just disabled it in the Services control panel:
- Launch Services.msc.
- Locate Razer Game Scanner in the list of services.
- Double-click the service's entry, then click Stop and set the Startup type field to Disabled and then click OK.
6 comments:
It's even worse that what you say. I found my computer being very laggy from time to time. Today I discovered that from within the task manager you can enable the I/O columns in the process view.
To my disappointment, I discovered that the Razer's game scanner server has more write I/O operations than ever other process on my computer combined! Damn you Razer!
thanks for the quick and easy fix
thanks for this, hopefully improves performance
It's 2019 and I still needed this, thanks!
THANK YOU SO MUCH
Post a Comment