Jump to content

Digitsoft

Members
  • Content Count

    10
  • Joined

  • Last visited

About Digitsoft

  • Rank
    New Member
  1. rf-chrome-nm-host.exe is used for all processes and not specific to Chrome - confirmed via Roboform. If you want to see what this process (and others are up to), download and run procmon from MS. https://docs.microsoft.com/en-us/sysinternals/downloads/procmon Add a filter to monitor processes that start with rf, capture for a few seconds, and you'll see the RF process constantly hitting MS Accessibility components.
  2. I don't know your situation directly, but with Roboform and Chrome there's an issue not related to MB. I tracked this down and worked with Roboform via tickets, but they have no fix - it's due to Windows Accessibility components. Roboform uses Microsoft Accessibility components to track various items and you can't disable the accessibility in Windows. I had to disable Roboform in Chrome and use LastPass in Chrome - no choice.
  3. Software (all current as of Jan 13, 2018) OS: Win 7 x64 SP1 MB: Premium 3.3.1 AV: eSet v11 Roboform: 8.4.6.6 Chrome x64 When I'd run Chrome with Roboform enabled, I'd notice lag and high CPU use (2-5% constant) for the Roboform process (rf-chrome-nm-host.exe) attached to Chrome. This does not occur when I use Firefox x64 with Roboform enabled - the same executable is used for Firefox and the filename is not specific for Chrome (weird huh?). I used Procmon (from Sysinternals) to see what the Roboform process was doing only when Chrome was in use. There's a constant registry lookup cycle along with file lookup. I had been trying to figure out what the issue was, but finally involved the Roboform support team. They looked at my Procmon log and ran some internal tests - they said that eSet and/or MB were injecting into those processes. I tested many scenarios and in the end they were correct - MB was the culprit. With MB disabled I can run Chrome with Roboform and no spikes in CPU occur. I then went further to test a brand new Chrome profile with nothing enabled other than Roboform - same issue. I then added the Roboform executable in question to the MB exclusions list, but the CPU issue still exists only in Chrome. The CPU issue with this process only happens with MB enabled, so I now have to choose between either MB or using Roboform in Chrome. Ideas?
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.