Hawaii Posted August 13, 2017 ID:1152995 Share Posted August 13, 2017 RTProtectionDaemon memory consumed keeps increasing now over 1.5 GB . I need to force quit to empty it or restart my computer. Link to post Share on other sites More sharing options...
ManfredLC Posted August 14, 2017 ID:1153125 Share Posted August 14, 2017 Hi Hawaii, here's what I did to solve this permanently (quoting myself from a recent thread): "I had the same issue using Malwarebytes on a French Mac running El Capitan, only worse: the daemon was using 600MB of memory after only 2 hours of use, and rising! Here's what I did 5 days ago: 1) Deactivate RealTime protection 2) Kill the daemon via Activity Monitor. The deamon relaunched immediately, but it's been using between 53 Mb and 63 Mb of memory ever since." Hth Manfred Link to post Share on other sites More sharing options...
treed Posted August 14, 2017 ID:1153316 Share Posted August 14, 2017 We're investigating this, and I'll get back to you. Link to post Share on other sites More sharing options...
ManfredLC Posted August 14, 2017 ID:1153370 Share Posted August 14, 2017 Ok Thomas, thanks for looking into this! Hope you can fix it. Manfred Link to post Share on other sites More sharing options...
treed Posted August 17, 2017 ID:1154521 Share Posted August 17, 2017 We think we've found the source of the problem, and should be able to get that fixed in a September release. Link to post Share on other sites More sharing options...
robertleeblairjr Posted August 17, 2017 ID:1154526 Share Posted August 17, 2017 I can confirm that this problem has plagued my system with macOS 10.12.6 since installing the newly released Malwarebytes version 3.x. If I have "Real-Time Protection" enabled, then the memory consumption increases to as large as 1GB before I've disabled it and killed the process. If I leave the "Real-Time Protection" disabled, then I do not experience this growing memory problem with "RTProtectionDaemon". Link to post Share on other sites More sharing options...
ManfredLC Posted August 17, 2017 ID:1154540 Share Posted August 17, 2017 49 minutes ago, treed said: We think we've found the source of the problem, and should be able to get that fixed in a September release. Thanks for the good news! :-) Manfred Link to post Share on other sites More sharing options...
robertleeblairjr Posted August 17, 2017 ID:1154546 Share Posted August 17, 2017 20 minutes ago, ManfredLC said: Thanks for the good news! :-) Manfred Not sure which you believe is good about the news; the developers potentially discovering the problem or taking almost a month to release an update which is the selling feature of this program to gain subscribers. Otherwise, it's just a revised look of their older product which was more stable. Link to post Share on other sites More sharing options...
joshvickerson Posted August 24, 2017 ID:1156608 Share Posted August 24, 2017 On 8/17/2017 at 10:31 AM, robertleeblairjr said: taking almost a month to release an update I have a hunch this delay is related to the launch of macOS 10.13, which MWB doesn't work on because, IIRC, 10.13 is dropping support for kernel extensions which MWB currently relies on. I too am having the problem with bloated RAM usage; at nearly 3GB after my Mac has been on for a couple days. Link to post Share on other sites More sharing options...
robertleeblairjr Posted August 24, 2017 ID:1156702 Share Posted August 24, 2017 4 hours ago, joshvickerson said: I have a hunch this delay is related to the launch of macOS 10.13, which MWB doesn't work on because, IIRC, 10.13 is dropping support for kernel extensions which MWB currently relies on. I too am having the problem with bloated RAM usage; at nearly 3GB after my Mac has been on for a couple days. Fairly valid assumption. I can confirm the same malfunction exists, as the previous, 3.x version. The newest version, 3.0.2.422, that was released in the last couple of days is still having the runaway memory problem. My clean installation, not an upgrade, had RTProtectionDaemon grow to almost 2GB within 24 hours. I disabled Real-Time Protection and killed the process. Link to post Share on other sites More sharing options...
robertleeblairjr Posted August 24, 2017 ID:1156716 Share Posted August 24, 2017 (edited) 5 hours ago, joshvickerson said: I have a hunch this delay is related to the launch of macOS 10.13, which MWB doesn't work on because, IIRC, 10.13 is dropping support for kernel extensions which MWB currently relies on. I too am having the problem with bloated RAM usage; at nearly 3GB after my Mac has been on for a couple days. I just read an Apple Support page that references the changes to kernel extensions. Apple is not removing or eliminating support for third-party kernel extensions but are introducing a new feature called "User Approved Kernel Extension Loading". https://support.apple.com/en-us/HT208019 The feature which is described as being a secure kernel extension loading procedure is described in more detail on the Apple Developer site. https://developer.apple.com/library/content/technotes/tn2459/_index.html#//apple_ref/doc/uid/DTS40017658 Edited August 24, 2017 by robertleeblairjr Link to post Share on other sites More sharing options...
robertleeblairjr Posted August 26, 2017 ID:1157400 Share Posted August 26, 2017 I am curious as to if there's a correlation to the 'RTProtectionDaemon' process virtual memory size and the leaking of real memory. The current virtual memory size of 'RTProtectionDaemon' is approximately 2.5 GB, even though, the real memory use is less than 50 MB after I disabled Real-Time Protection. However, the increase in real memory size used by the process appears to reach virtual size. However, I killed the process before allowing it to go beyond 2 GB. Link to post Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now