My 15" rMBP became extremely sluggish when using Mail to a point it just became unusable.
I'm not talking about the usual scroll lag, but much worse. I scrolled at around 1 FPS and everything I clicked on took around 5 seconds to respond. If I insisted using it, the whole OS X UI would just eventually crash and everything (including Mail, Finder windows, menubar items) would just restart.
When looking at OS X's Console, I saw there were multiple errors per second all related to a Tracking Area (not sure what that is).
I actually found the solution to this problem. This post isn't to ask for help but rather to help those who will Google about this glitch and find the solution. I also suspect the problem is not exclusive to Mail.
Now for the solution: I used OnyX to rebuild LaunchServices. You'll need to go in the "Automation" tab and check "Rebuilding: LaunchServices" and then click the Execute button. The problem (and all the entries in the Console) were gone after.
I'm not talking about the usual scroll lag, but much worse. I scrolled at around 1 FPS and everything I clicked on took around 5 seconds to respond. If I insisted using it, the whole OS X UI would just eventually crash and everything (including Mail, Finder windows, menubar items) would just restart.
When looking at OS X's Console, I saw there were multiple errors per second all related to a Tracking Area (not sure what that is).
Code:
CGSSetTrackingAreaOption returned CG error 1001
WindowServer CGXSetTrackingAreaEnabled : Invalid tracking area
WindowServer CGXRemoveTrackingArea WindowServer window invalid tracking area
CGSAddTrackingRect: Region creation failure
Error in CGSAddTrackingRect (1000)I actually found the solution to this problem. This post isn't to ask for help but rather to help those who will Google about this glitch and find the solution. I also suspect the problem is not exclusive to Mail.
Now for the solution: I used OnyX to rebuild LaunchServices. You'll need to go in the "Automation" tab and check "Rebuilding: LaunchServices" and then click the Execute button. The problem (and all the entries in the Console) were gone after.