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. I then added the Roboform executable in question to the MB exclusions list, but the CPU issue still exists only in Chrome. I then went further to test a brand new Chrome profile with nothing enabled other than Roboform - same issue. With MB disabled I can run Chrome with Roboform and no spikes in CPU occur. I tested many scenarios and in the end they were correct - MB was the culprit. They looked at my Procmon log and ran some internal tests - they said that eSet and/or MB were injecting into those processes.
I had been trying to figure out what the issue was, but finally involved the Roboform support team. There's a constant registry lookup cycle along with file lookup. I used Procmon (from Sysinternals) to see what the Roboform process was doing only when Chrome was in use. This does not occur when I use Firefox 圆4 with Roboform enabled - the same executable is used for Firefox and the filename is not specific for Chrome (weird huh?). 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. Software (all current as of Jan 13, 2018)
0 kommentar(er)
