Slashdot Mirror
Malwarebytes Released Two Bad Web Protection Updates (csoonline.com)
Malwarebytes had a bad day Saturday, pushing out an update "that gobbled up memory and CPU resources and turned off web protection," reports CSO.
The company's forums lit up with complaints that the software was hogging 90 percent or more of memory and CPU resources. One thread about RAM usage currently is 37-pages long. Aware of the problem, Malwarebytes tweeted that "all hands" were on deck to resolve the issue. Unfortunately, even though a new update package was pushed out in about an hour, it did not fix the problem. Even after rebooting their computers, some users reported that their systems locked up as soon as the Malwarebytes Service process started as it ate large amounts of RAM.
"Two bad updates later, Malwarebytes released a fix," CSO reports, noting the company's blog post with steps to resolve the issue.
Long-time Slashdot reader marquis111 shares a link to an apology from Malwarebytes CEO Marcin Kleczynski, who says that he'll be "personally available" to discuss the problem on both the forums and at his personal email address.
"Two bad updates later, Malwarebytes released a fix," CSO reports, noting the company's blog post with steps to resolve the issue.
Long-time Slashdot reader marquis111 shares a link to an apology from Malwarebytes CEO Marcin Kleczynski, who says that he'll be "personally available" to discuss the problem on both the forums and at his personal email address.
Malwarebytes is closed source software. It could literally be doing anything to your system. You have no control over it, or what it does. So you basically are trusting some corporation.
Uh, I'm afraid your point was completely lost due to the fact that the people who need Malwarebytes aren't running FOSS.
That also includes the OS.
ever since version 2 and the loss of the lifetime update model, then further down the crapper with version 3 and the forced trial mode on install and always-on services (even in 'free' mode).
if you want a simple on-demand scanner to supplement your antivirus product, just use adwcleaner. it's better and faster, anyway (until they fuck that up, too); then hitmanpro (free scan mode is good enough) as a double-check (also crazy-fast and very good)
This occurs quite regularly with no acceptable excuse.
Step 1. - Vendor fucks up royally.
Step 2. - Customers complain.
Step 3. - Vendor runs around like a chicken without a head frantically attempting to fix whatever they fucked up almost always with even more lax quality standards than what was necessary to fuck up in the first place.
Step 4. - Customer predictably complains about fix not working or breaking even more shit.
Step 5. GOTO Step 3.
Lets put aside the problem of original fuckup and focus on the inexcusable portion of this. Mistakes / oversights happen.
Step 3 is where you ROLLBACK what you broke. It is NEVER about working overtime to fix what you broke by shipping out new code as soon as it compiles. Failure to plan ahead for this contingency and have a tested working rollback strategy carries predictable consequences. THIS is the failure this company should be apologizing for and the lesson they SHOULD have learned. Yet I'm quite certain it did not even occur to them.