Torre

Thanks everyone. Interesting data points with a big spread... so once again no conclusive evidence either way.

Well that seems consistent then. I certainly hope the MBAM folk are listening!

Thanks brcd. If you don't have a lot of music, movies, photos and don't do a lot with large files stored locally on your disk (such as Virtual Machines, don't worry if you don't know what these are), you probably don't have a large home directory. Easiest way is to click on a Finder window, then type Shift-Cmd-H, then Cmd-I (shortcut for Get Info). Make sure you don't click on anything in between the two key sequences. You should see the info window pop up with a house icon and your login name on the top left, and the size of your home folder is on the top right. For me, after trying

Thanks, brcd. In my case I tested with 5 different accounts on 4 different machines. Most of them showed ~1% CPU with infrequent jumps to 20%/40%. On the "problem" account it shows mostly ~15% with more frequent jumps to 60-80% (this is a long term estimated average; I've also seen it drop to sub-1%). This is also the account which has the largest home directory so I wonder if that has anything to do with the CPU usage. Would you be ok posting how much disk space your home directory uses? Mine as mentioned is >280GB.

MBAM support was very responsive in the end for me. However I am quite disappointed that the only suggested remedies were "remove browser extensions" (aside from one or two the rest are needed) and "remove your Library/Caches directory because it's larger than normal" (most of these were iTunes / Apple Music files, so not surprising they are large as I have a LOT of music). Neither helped. In my case MBAM CPU hogging (as opposed to occasional spikes) seem to be related to something else such as stuck installs. MBAM just seems very sensitive and happy to eat a lot of CPU at the slighte

So I promised to post the findings of the support ticket. Here we go. After testing MBAM across 4 machines and at least 5 accounts, There was no root cause found and I am still having high but not obscene CPU usage on one account (call this machine "Mac 1") One of the test machines (Mac 2) was more or less of the same vintage and used in a similar manner to the "problem" account on Mac 1, it did not exhibit high CPU Other accounts on Mac 1 also did not exhibit high CPU, however I was not able to replicate usage as closely I as I did on Mac 2 The only possibility remain

Adding my voice to the many who find v4.5.15 a CPU hog. I'm a big fan of Malwarebytes but only recently paid for premium as competitors (Avira, Avast, BitDefender, etc.) give it away free. Imagine to my surprise when I see RTProtectionDaemon hogging CPU constantly. It is never below 20% CPU, it is mostly above 60% CPU, it is often above 85% CPU on my 2015 MBP on Catalina 10.15.7. This issue appears to have been present since at least July without a fix. WORST of all, support does not respond. Opened a ticket yesterday and no human has said "boo" after 24 hours. I can't track my