RTProtectionDaemon above 90% CPU usage, virtual memory 4.5 GB!

[Dan_Bln]

I saw another thread which did not seem to resolve the issue but moving away from malwarebytes. As I am a paying customer, I would like a resolution or a refund for the remaining next 12 months of paid fees. 

Perhaps anyone else has an idea how to fix it?

 

- after awake from sleep my macbook camera would not work in chrome for a meet.google.com session.
- reboot of the system did not resolve either
- strange behavior. 

- checking activity monitor  the trouble instigator was identified! --> RTProtectionDaemon above 90% CPU usage, virtual memory 4.5 GB! 

- killing the service / process from activity monitor helped me to use my macbook again. 

Kindly investigate and provide a fix. (created ticket 2383875 with malware support) 

 

Hardware Overview:

  Model Name:    MacBook
  Model Identifier:    MacBook9,1
  Processor Name:    Intel Core m7
  Processor Speed:    1,3 GHz
  Number of Processors:    1
  Total Number of Cores:    2
  L2 Cache (per Core):    256 KB
  L3 Cache:    4 MB
  Memory:    8 GB
  Boot ROM Version:    MB91.0172.B00
  SMC Version (system):    2.35f105

SDD:
available:    93,39 GB (93.392.633.856 bytes)
  Capacity:    249,68 GB (249.678.528.512 bytes)

  File System:    Journaled HFS+
  Writable:    Yes
  Ignore Ownership:    No

  BSD Name:    disk1

  Logical Volume:
  Revertible:    Yes (unlock and decryption required)
  Encrypted:    Yes
  Encryption Type:    AES-XTS
 

  Physical Volumes:

disk0s2:
  Device Name:    APPLE SSD AP0256J
  Media Name:    APPLE SSD AP0256J Media
  Size:    250,04 GB (250.035.572.736 bytes)
  Medium Type:    SSD
  Protocol:    PCI-Express
  Internal:    Yes
  Partition Map Type:    GPT (GUID Partition Table)
  Status:    Online
  

[treed]

Dan,

I see that you've already started a customer support ticket - and I see that Aditya has responded to it with a request for more information - which is what I would have recommended. We would need to gather more information about your system, and that isn't something that should happen on a public forum.