jg5112
Level 1 (4 points)
Notebooks

Q: Too much wired memory

Somehow my computer is using 13GBs of wired memory. This is not the first time it has happened... it seems that whenever I close out an app all the memory it was using goes into wired or something. My computer is barely running like this and I have tried multiple memory cleaning apps which have done nothing.

 

Screen Shot 2016-08-22 at 11.02.39 PM.png

 

And it's still going up, it's over 13GBs now. Can anyone help me out?

Thank you!

MacBook Pro (15-inch Mid 2012), OS X Yosemite (10.10.5)

Posted on Aug 22, 2016 8:15 PM

Close
jg5112

Q: Too much wired memory

  • All replies
  • Helpful answers

  • by chris_g1,

    chris_g1 chris_g1 Aug 23, 2016 2:10 PM in response to jg5112
    Community Specialists
    Aug 23, 2016 2:10 PM in response to jg5112

    Hello jg5112,

    Thank you for using Apple Support Communities. It's my understanding that you've been experiencing issues with wired memory and performance of your MacBook Pro. I can see how this would be concerning, especially since this has occurred before. I want to help get this resolved with you.

    First I recommend using the Activity Monitor to determine which applications and programs are using the memory. For additional information on using the Activity Monitor, please use the link below.
    Use Activity Monitor on your Mac

    If you're still unable to determine which apps are causing the issue, try testing in safe mode. This will allow your Mac to run certain checks and prevent startup logins. Use the link below for assistance with how to start up in safe mode and the steps to take if the issue doesn't occur in safe mode:
    Try safe mode if your Mac doesn't finish starting up

    Have a great day!

  • by jg5112,

    jg5112 jg5112 Aug 23, 2016 2:15 PM in response to chris_g1
    Level 1 (4 points)
    Notebooks
    Aug 23, 2016 2:15 PM in response to chris_g1

    Activity monitor is what showed me all that wired memory. None of the apps in there app up even close to how much was being used.

     

    I will try safe mode, but what exactly should I do? Just use my computer normally and see if the problem still occurs?

  • by steven_a1,

    steven_a1 steven_a1 Aug 24, 2016 5:34 AM in response to jg5112
    Community Specialists
    Aug 24, 2016 5:34 AM in response to jg5112

    Thank you for following up. When in safe mode use your Mac as you normally would. Check to see if it is performing the same and if the memory is being used. If the issue goes away in safe mode then it's very possible login items could be the cause. Use the link below for assistance with removing incompatible login items:
    OS X Yosemite: If you think you have incompatible login items

    If the issue persists in safe mode then it's possible the cause is user specific settings or files. The next step would be to test this in another user. Please use the link below for steps to test in another user: How to test an issue in another user account on your Mac

    Cheers

  • by jg5112,

    jg5112 jg5112 Aug 24, 2016 1:03 PM in response to steven_a1
    Level 1 (4 points)
    Notebooks
    Aug 24, 2016 1:03 PM in response to steven_a1

    I tried safe mode out and my computer was completely un-useable. Half the applications I opened crashed, I had no sound, and more internet pages I loaded bugged out. I did notice the problem still happening too, but it seemed to stop happening when I quit out of Chrome. So I tried booting my computer normally and not using Chrome but it still happened. So it seems that the issue only doesn't happen in safe mode with Chrome not started up. Though I only waited like 10 minutes. Even though it still happens with Chrome closed with my computer started normally the wired memory still seems to go up more slowly with it closed.

    Is there not any way I can check the break up of what the wired memory is being used for?

    I will try testing another user next.

  • by jg5112,

    jg5112 jg5112 Aug 24, 2016 11:28 PM in response to jg5112
    Level 1 (4 points)
    Notebooks
    Aug 24, 2016 11:28 PM in response to jg5112

    After doing some more testing I am 100% sure that it is Google Chrome now. I will try looking into Chrome related issues.