Jump to content

raylist

Members
  • Content Count

    6
  • Joined

  • Last visited

About raylist

  • Rank
    New Member
  1. I opened the ticket. I also created the log file, but I'm reviewing that before I send it. It seems like a LOT of data (27.2MB) and even includes the Mac system install log back to October of last year. I'm leaning toward not sending this and just eating what I paid for MWB and removing it from my computer. It seems to me I might be safer that way then sending all this data 'who knows where'. Keeping my data contained is why I bought MWB in the first place. I spent my career as a programmer working for banks, so maybe I'm overly sensitive to where data goes. As an old Mainframe guy, I have my own little "OmegaMon" here (mainframe techs will know what that is) in the form of "iStat Menus" by which the state of my machine in many aspects is easy to monitor. I have to think long and hard about this zip file. I see that @Popeye has replicated the issue, but with smaller numbers. I'm running MacOS Catalina 10.15.2 on a Mac Book Pro with 16GB of memory. At boot, RTProtectDaemon starts with 122MB. It gains close to 100MB with every scan, with no end in sight.
  2. I just tried something and found that every time I run a scan, it adds about 100MB to the task. I ran the first scan, and it went to 320. Ran another scan and it went to 415BMB. Ran a third scan and now it is sitting at 512MB. Huston, we have a problem!
  3. I will log a ticket a little later when I have more time. For now, a little more data: Yesterday, I rebooted my Mac (something I don't do often). The memory use of that task was then 118MB after the restart. This morning, it has climbed to 221MB. Sure seems like a memory leak to me.
  4. I purchased Malwarebytes for my Mac. After a week of use, I noted that RTProtectionDaemon was using 10 GB of memory. I killed the process, removed Malwarebytes, re-installed the program and have been monitoring it. The first 2 days, RTProtectionDaemon was a little over 200 MB, then it jumped to 319MB. Now after a few more days it is using 519 MB. That seems like quite a bit of my memory being used by that task, and it seems to be growing. Certainly better than the 10 GB originally used, but still quite a bit. Any tips regarding this, or should I dump this program?
×
×
  • 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.