I own a mid 2011 Macbook Air. I recently installed Mountain Lion, and it's been pretty great. One issue I have is that the shutdown time takes 15 - 20 seconds now. It used to take like 2 or 3.
So weird too, I would have expected startup time to also increase if my shutdown time increased, but startup time is the same if not better.
Anyone else with this issue? Not sure how to fix this other than a clean install, which I don't really want to do (no backup drives on me at the moment and can't really afford a new one right now).
----------
EDIT (FIXED):
Haha damn, I figured it out. Of course I figure it out a second after I make the thread (this has been an issue for a couple days..didn't put two and two together until right now).
I recently installed Cubby (new cloud storage solution) on my computer. It's constantly been on, and it was increasing my shutdown time. I just exited out of the program before turning off my computer, and it was back to a few seconds.
Mods can lock or leave open for people who may have the same issue. Seems like a bug with Cubby (most likely) or maybe a bug with the way Mountain Lion handles background services?
So weird too, I would have expected startup time to also increase if my shutdown time increased, but startup time is the same if not better.
Anyone else with this issue? Not sure how to fix this other than a clean install, which I don't really want to do (no backup drives on me at the moment and can't really afford a new one right now).
----------
EDIT (FIXED):
Haha damn, I figured it out. Of course I figure it out a second after I make the thread (this has been an issue for a couple days..didn't put two and two together until right now).
I recently installed Cubby (new cloud storage solution) on my computer. It's constantly been on, and it was increasing my shutdown time. I just exited out of the program before turning off my computer, and it was back to a few seconds.
Mods can lock or leave open for people who may have the same issue. Seems like a bug with Cubby (most likely) or maybe a bug with the way Mountain Lion handles background services?