Jump to content

kc6108

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About kc6108

  • Rank
    New Member

Recent Profile Visitors

571 profile views
  1. Hmm, it seems the TestFlight beta testers aren't being fully utilized. That is unless version 1.3 is really 1.2.2 (or very close I mean). No big deal. It’s just I’m a Software Engineer by trade. It may have been a long time since I’ve actually coded, but I’m intimately familiar with the SDLC. I take my beta testing responsibilities seriously. I’ve also been a Malwarebytes user, supporter, and proponent for over 10 years. This mix isn’t good for my OCD lol
  2. I noticed Malwarebytes 1.3.0 is available in the AppStore, but I’m still testing the 1.2.2 version. I would have liked to test 1.3.0 because I’ve submitted several bugs that I’d like to test. I don’t have a Pro subscription, so I can’t install the AppStore version to test. Please advise as I’m still not interested in purchasing a subscription but still want to help you guys test as I use MBAM extensively on other platforms (with lifetime licenses, etc). I’d rather not get a trial subscription from you guys as I’d rather have the Beta version installed. I go through my TestFlight testing list a
  3. I am experiencing almost constant high CPU usage running what I believed was the beta version of MBAM 3.0.1.389. Activity Monitor shows RTProtectionDaemon as the culprit. Less than a month ago I installed a fresh copy of macOS Sierra (10.12.6) onto my mid-2010 MacBookPro. It was lightning fast until I installed MBAM. I also have Sophos Home installed (see NOTE 3 below). I figured I'd see Sophos and MBAM utilizing high CPU together (running into one another), but that does NOT seem to be the case. Just to make sure I: 1) Uninstalled Sophos and there was NO change in CPU utilization and 2)
Back to top
×
×
  • 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.