Malwarebytes Released Two Bad Web Protection Updates (csoonline.com) 70
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.
Who knows? (Score:1)
Re:Who knows? (Score:5, Insightful)
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.
Re: (Score:1)
Re: (Score:2)
Re: (Score:2)
You are already trusting corporations for your water and food. Closer to computing, you are likely also trusting Intel for your chipset with their beautiful IME nonsense. Trusting someone for malware protection is not so special.
MalwareBytes installed a tiny steering wheel ... (Score:3, Funny)
... in my pants yesterday because it was drive'n me nuts!
OK (Score:2)
Re: (Score:1, Troll)
Re: (Score:1, Troll)
Re: (Score:2)
Re: At work today (Score:2)
Pfft, a promise he knows he won't have to deliver! (Score:3)
Re: (Score:2)
Yeah, it's pretty unlikely that anyone would have access to two computers in 2018.
mbam has gone to shit.. (Score:2, Insightful)
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)
Already Uninstalled. (Score:2)
Until they fix it I think I will NOT be reinstalling it.
Re: (Score:2)
Re: Already Uninstalled. (Score:2)
who uses it anyway (Score:2)
What timing... (Score:1)
the timing couldn't have been worse for my household. I dug up my old lifetime keys friday after about 5 years to install it on my childrens playroom computer and my backup pc and staurday both systems were unusable with malwarebytes using 90+% cpu and 50+% HD. I actually uninstalled both when I got home Saturday with the thought 'Wow, Malwarebytes has totally gone to crap, I remember when it used to be good". I had planned to look up and find out what the hell happened to the program today when this artic
Inexcusable persistant stupidity (Score:4, Insightful)
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.
HUGE memory leak, Maximum CPU usage (Score:2)
Recent automatic updates to Malwarebytes software have been destructive in other ways, apparently. The company says Malwarebytes can and should co-exist with other anti-malware softwa
Yup.... (Score:1)