Previous 1 3 4 5 6 7 Next 99 Replies Latest reply: Jul 17, 2011 2:43 PM by R C-R Go to original post Branched to a new discussion.
  • mlsommer Level 1 Level 1 (0 points)

    I applied this fix (thanks Greg!!) a week or two ago after MRT just about "melted down" ;-) my macbook pro following the security update. Things were working fine until...

     

    OSX update to 10.6.8 last night. Now MRT is back in full-effect constantly restarting and running like crazy. The CPU utilization is regularly at 99-100% for that process (I love how the top & Activity Monitor show 200% for your total utilization...kinda like saying the processor is 200 proof I guess).

     

    Anyway, I'm going to try to fix permissions again first to see if that resolves it, but if not, I'm back to using the fix Greg recommended above again. And, potentially, EVERY TIME APPLE RELEASES A NEW OS UPDATE.

     

    Seriously, there's got to be a root cause here that can be addressed. Any suggestions? Please don't say reinstall Mac OSX. Fine, I can do that, but seriously, people make fun of Windows because everyone's always telling you to "reboot" to fix issues, but you're going to tell me to reinstall Mac OS and that's "really no big deal."

    Please.  </end rant>

  • mlsommer Level 1 Level 1 (0 points)

    Yeah, that was of no use. Applying the fix Greg recommended. Again.

  • MadMacs0 Level 5 Level 5 (4,415 points)

    mlsommer wrote:

     

    Seriously, there's got to be a root cause here that can be addressed. Any suggestions? Please don't say reinstall Mac OSX. Fine, I can do that, but seriously, people make fun of Windows because everyone's always telling you to "reboot" to fix issues, but you're going to tell me to reinstall Mac OS and that's "really no big deal."

    Please.  </end rant>

    I think the problem was that we focused Apple on the continuing problems of the XProtect process not updating as it should.  The MRT issue was short lived and may have involved fewer users, so it didn't get the attention it should have.  I think the only way it will get the focus it deserves is if those of you who experience the problem and still have AppleCare support give them a call and get it on the books.  If everybody simply follows the quick fix laid out by Greg and others, the problem will probably follow you all with every update.

  • Greg Mihran Level 1 Level 1 (0 points)

    New Update - I just installed the OS X 10.6.8 update today which once again created the MRT process (Malware Removal Tool). I watched it for 15 minutes to see what it would do on a fresh restart with no other programs running.  I have a MacBook Pro, 2.66 GHz Intel Core 2 Duo, 4 GB DDR3 memory.

     

    The MRT process consumed from 0.1% to 99.9% of CPU, fluctuating broadly within that range with every refresh.  I waited to see if it would settle down like the old Windows Security updates would do after a few minutes, but to no avail.  I tried running a few other programs simultaneously to see if it would be pushed to the background, but it would not. 

     

    MRT ran with High Priority (Root, Intel 64 Bit Process), interfering with system performance utilizing:

    • 0.1%-99.9% CPU
    • 100MB-300MB Real Memory
    • 2 Threads
    • 30 Ports

     

    I performed the following two commands to unload and delete the process ...

     

    Open Utilities/Terminal, run the command to unload the process:

    • sudo launchctl unload /System/Library/LaunchDaemons/com.apple.mrt.plist
    • copy and paste that command, enter your password, wait about 10 seconds

    Open Finder, select the file and Move to Trash:

    • /System/Library/LaunchDaemons/com.apple.mrt.plist
    • enter your password to complete the removal

    Restart.

     

    All worked and was back to normal after the restart.  Like many other recent Windows converts to Apple, this issue reminded me all too much of what I left behind and I hope that it is not a precursor of what's to come from OS X 'Security' updates.

     

    Greg

  • ChrisConnelly Level 1 Level 1 (0 points)

    Greg's fix worked for me as well.  It seems odd that we have to delete a security update process in order to keep the CPU from being overrun.  I took my MBP into Apple and they claimed it was not a known issue.  Isn't the Apple logo at the top of this page?? 

     

    Do we know definitively what is "causing" this issue.  We all seem very good at identifying the symptom, has anyone figured out the actual root cause?

  • MadMacs0 Level 5 Level 5 (4,415 points)

    ChrisConnelly wrote:

     

    Greg's fix worked for me as well.  It seems odd that we have to delete a security update process in order to keep the CPU from being overrun.

    And that's an important point.  Although this process deletes itself after completion, I don't think any of us knows whether it had finished or even started to accomplish what it was designed to do.

    I took my MBP into Apple and they claimed it was not a known issue.  Isn't the Apple logo at the top of this page?? 

     

    Do we know definitively what is "causing" this issue.  We all seem very good at identifying the symptom, has anyone figured out the actual root cause?

    Good for you on taking it to Apple.  I've been encouraging folks to do that.  I think the problem has been that the fix came too fast and was too easy, so nobody bothered to take the problem to Apple over the phone or in the store.  Perhaps it was because their AppleCare had expired, or because we all focused on other issues with the update or just had better things to do after it was fixed.

     

    FYI, Apple provides us with this forum, but it's run by the user community.  Apple does drop in periodically to monitor, but reporting it here is not the official way they do business.  Users start here: http://www.apple.com/support/contact/

     

    I have not read here or elsewhere of even a theory on the cause.  Again, I think we jumped on the cure and moved on to what were to each of us bigger issues.  The danger, of course, is that the MRT process did not accomplish what it was designed to do and leaves the user with malware on his computer that he believes has been taken care of.  There are also probably users out there who are having this problem, are unaware of this forum and wonder why their fans are running so high.

  • powerbook1701 Level 3 Level 3 (550 points)

    Whatever is triggering this for some and not others, I have two MBP's that updated fine with no fan issues. It would be nice if we could tie it to something specific. Your right, if the process doesn't complete as it should, the user could be at risk...

  • sspooner Level 1 Level 1 (0 points)

    Same problem here.

    Clean permissions scan and a clean disk verify scan.

    I have to manually remove MRT each time I reboot.

     

    MRT != Malware Removal Tool

    MRT == Malware REPLACEMENT tool.

     

    :-)

     

    I have no malware on my machine, so apple kindly provided me some.  MRT.

  • MadMacs0 Level 5 Level 5 (4,415 points)

    sspooner wrote:

     

    I have to manually remove MRT each time I reboot.

    Well, this is something I've not heard before.  Please tell us exactly what you removed and from where and did you empty the trash afterward?  I don't see how it could be recreating itself without reinstalling the update.

  • sspooner Level 1 Level 1 (0 points)

    Ah, when I say "remove" I mean remove from the current running processes, not remove the the actual file from disk.

  • WZZZ Level 6 Level 6 (12,640 points)

    sspooner wrote:

     

    Ah, when I say "remove" I mean remove from the current running processes, not remove the the actual file from disk.

    That's why. Killing a process that is always set to run will only stop it until the next reboot. From earlier in the thread:

     

    Interz, no need to wait and suffer, the solution (for me) took less than 10 seconds.  Take a read of the thread before your post, it's a two-step process.

     

    Open Utilities/Terminal, run the command to unload the process:

     

    sudo launchctl unload /System/Library/LaunchDaemons/com.apple.mrt.plist

     

    Open Finder, select the file and Move to Trash:

     

    /System/Library/LaunchDaemons/com.apple.mrt.plist

     

    Restart.  Worked for me.

     

    Greg

     

    Message was edited by: WZZZ

  • sspooner Level 1 Level 1 (0 points)

    Yes, the point I was trying to get across is that my disk is clean. No perms problems and a verify disk comes back clean, so the speculation of clobbered perms or files doesn't seem valid.

  • WZZZ Level 6 Level 6 (12,640 points)

    Has nothing to do with Permissions or Directory problems. It appears to be a bug that, for some reason, is catching a number of users.

  • Greg Mihran Level 1 Level 1 (0 points)

    Spooner's experience calls for a minor tweak to our 'fix' ...

     

    Open Utilities/Terminal, run the command to unload the process:

    • sudo launchctl unload /System/Library/LaunchDaemons/com.apple.mrt.plist
    • copy and paste that command, enter your password, wait about 10 seconds

     

    Open Finder, select the file and Move to Trash:

    • /System/Library/LaunchDaemons/com.apple.mrt.plist
    • enter your password to complete the removal
    • verify that com.apple.mrt is not in Trash (if so, delete it)

     

    Restart.

     

    It is imperative that com.apple.mrt.plist is unloaded, moved to Trash, and does not remain in Trash.  Once completed, the process will no longer run on any Restart.

     

    Editorial comment - this 'fix' only addresses the sympton and does not determine the cause.  The 10.6.8 MRT affected my newer MacBook Pro (2.66 GHz, vintage 2010) but not my MacBook Pro (2.4 GHz, vintage 2008) so far.  Both are running the same OS 10.6.8 and both are Intel Core 2 Duo.  

     

    We should keep this discussion open until Apple/the community determines the cause.  The MRT CPU consumption on the newer MacBook Pro is unacceptable and, therefore, requires this 'fix'.  In this case, the Apple MRT ultimately become the malware that needs to be removed - go figure.

     

    Greg

  • powerbook1701 Level 3 Level 3 (550 points)

    chiming in, this issue did not affect a 2010 MBP nor a 2008 MBP.  There has got to be some common 3rd party app or setup that is causing this issue..

Previous 1 3 4 5 6 7 Next