Odd Console errors associated with Exposé and/or Dock process

Discussion in 'macOS' started by WiLLGT09, Mar 22, 2011.

  1. WiLLGT09 macrumors regular

    WiLLGT09

    Joined:
    Nov 13, 2007
    #1
    Hi everyone,

    I seemed to have run across an series of error messages in my Console system.log.

    I have Exposé hot corners setup on my MacBook Pro and whenever I activate any Expose motion either via the hot corners or the keyboard short cut, I see a bunch of errors show up in Console:

    Mar 22 11:43:03 MacBook-Pro Dock[914]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 2: [0.000 0.000 0.000 0.000]
    Mar 22 11:43:03 MacBook-Pro Dock[914]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [0.000 0.000 0.000 0.000]
    Mar 22 11:43:03 MacBook-Pro com.apple.Dock.agent[914]: Tue Mar 22 11:43:03 MacBook-Pro.local Dock[914] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 2: [0.000 0.000 0.000 0.000]
    Mar 22 11:43:03 MacBook-Pro com.apple.Dock.agent[914]: Tue Mar 22 11:43:03 MacBook-Pro.local Dock[914] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [0.000 0.000 0.000 0.000]
    Mar 22 11:43:03 MacBook-Pro Dock[914]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 2: [0.000 0.000 0.000 0.000]
    Mar 22 11:43:03 MacBook-Pro com.apple.Dock.agent[914]: Tue Mar 22 11:43:03 MacBook-Pro.local Dock[914] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 2: [0.000 0.000 0.000 0.000]
    Mar 22 11:43:03 MacBook-Pro Dock[914]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [0.000 0.000 0.000 0.000]
    Mar 22 11:43:03 MacBook-Pro com.apple.Dock.agent[914]: Tue Mar 22 11:43:03 MacBook-Pro.local Dock[914] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [0.000 0.000 0.000 0.000]
    Mar 22 11:43:03 William-Brawleys-MacBook-Pro Dock[914]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 2: [0.000 0.000 0.000 0.000]
    Mar 22 11:43:03 MacBook-Pro com.apple.Dock.agent[914]: Tue Mar 22 11:43:03 MacBook-Pro.local Dock[914] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 2: [0.000 0.000 0.000 0.000]

    ...etc. there are quite a few more lines of similar errors after these, per each time I activate Exposé.

    Has anyone come across how to solve this? Other forum posts around the web mention trashing dock preferences and .db files, however those seem to be ineffective. Repairing Permissions doesn't do anything.

    I have recently done a clean install of Snow Leopard a couple weeks ago and did the update to 10.6.7 yesterday. I repaired permissions after the update.

    The only thing I can think of would be my previous install of OS X Lion on a second partition. I had MobileMe setup on that partition as well, which I know syncs Dock items, but if I remember correctly, I specifically told MobileMe Sync to not sync Dock items. However, I have erased that partition and reinstalled Snow Leopard like I mentioned above. Ever since uninstalling Lion, I did noticed some Dock icons moving back to their previous locations if I tried to move them around the Dock (however, a second moving of dock icons made them stick.) - but the Lion thing seems like a long shot.

    Anybody have anu ideas?

    Thank you.
     
  2. WiLLGT09 thread starter macrumors regular

    WiLLGT09

    Joined:
    Nov 13, 2007
    #2
    Solved

    Seems like I figured out the problem. Google Chrome dev build. OS X i guess just doesn't like it. Messes with the window system I guess, somehow.

    Going back to Safari solves the problem and no more console errors.
     
  3. WiLLGT09 thread starter macrumors regular

    WiLLGT09

    Joined:
    Nov 13, 2007
    #3
    unsolved...

    Ok, so I thought I had it figured out. It seems to happen if I also have Firefox 4 open. Same errors.

    It's not really that I can tell any difference in the way my computer is acting, so maybe I'm just being paranoid. But why are these messages showing up?
     
  4. netnothing macrumors 68040

    netnothing

    Joined:
    Mar 13, 2007
    Location:
    NH
    #4
    Just updated to Chrome 11 stable today and I too am getting these errors. Definitely has to do with Chrome, since I can't get them to occur if Chrome isn't running. Like you, I don't see any issues with the system, just noticed these filling up my logs.

    For Chrome I get these:

    For Firefox I get these:

    -Kevin
     
  5. netnothing macrumors 68040

    netnothing

    Joined:
    Mar 13, 2007
    Location:
    NH
    #5

Share This Page