Malwarebytes, however, notes that these systems were not affected if they weren’t running between Friday and Saturday at 11am Pacific Time.
To be able to capture past history, Process Explorer needs to be running, which isn't a problem since it can be minimized in the System Tray.
The next time a process causes a spike, just mouse over the icon in the System Tray and the pop-up will display the process name and percentage of utilization.
“The root cause of the issue was a malformed protection update that the client couldn't process correctly.
We have pushed upwards of 20,000 of these protection updates routinely.” The company recommends users to update Malwarebytes and to restart computers, but in case this doesn’t address the high CPU usage bug, they should download and run MB-CLEAN.
A bad Malwarebytes updates released the last weekend caused the main process of the security product, mbamservice.exe, to experience high CPU usage on Windows systems, up to the point where computers were nearly impossible to use.
Company officials quickly responded to the complaints posted online, and a fix is already available to address the bug.
Users are recommended to install the most recent update and reboot computers – two system restarts might be required, Malwarebytes says, because stabilizing the system doesn’t always take place after the first one.
As far as the cause of the bug is concerned, Malwarebytes says it was all because of a protection update shipped on Saturday morning.
Last Trade Price, Volume, Open Price and lots more) are given their own table staging table, each with a corresponding stored procedure that implements the merge.
For various reasons, each of the ~330 fields I wish to store (e.g.
“As a side effect of the web protection blocks, the product also spiked memory usage and possibly caused a crash.