Bug with Finder Windows

[Dejanire]

Hello,

Ever since this morning I have this problem with finder.
It has never happened to me before, and I have no idea why this is happening.

Since I have a hackintosh I don't feel like i can't post about this issue on a classic mac forum. This is why I'm here.

Can anyone help me fix this problem ?

Any advice will be greatly appreciated.

doing "Command-option-Escape" and Relaunching Finder fixes the problem, but only for a short period of time.

 

[qwerty123]

I'm having the *EXACT* same problem starting this morning. WTF!?

It's annoying. I'm on 10.9.5.

Some coincidence that this is happening today for the first time?

 

[magnamaduin]

Me three! (also on 10.9.5)

This is driving me crazy. I didn't update anything that day or the day before, so perhaps there was some sort of automatic rollout?

EDIT: Actually, I just remembered I DID update Flash in this timeframe.

DOUBLE EDIT: Uninstalled Flash, restarted. Problem persists. Neither Disk First Aid nor Avira find anything broken.

 

[magnamaduin]

While amateurishly digging in the console for an obvious cause on the 12th, I noticed I get this message every time I open a glitched window:

Finder: +[CATransaction synchronize] called within transaction

Which is well over my head but appears to have something to do with Core Animation:

CATransaction allows you to override default animation properties that are set for animatable properties. You can customize duration, timing function, whether changes to properties trigger animations, and provide a handler that informs you when all animations from the transaction group are completed.

Searching the console for messages related to CATransaction turns up this that occurred about a minute and a half after that day's first boot:

loginwindow[68]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

This seams to occur on login or on wake from sleep.


I also get this doozy every time the finder launches or relaunches:


3/15/16 4:02:07.765 PM Finder[3722]: (
0 CoreFoundation 0x00007fff8c05c25c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00007fff8b921e75 objc_exception_throw + 43
2 CoreFoundation 0x00007fff8c05f12d -[NSObject(NSObject) doesNotRecognizeSelector:] + 205
3 CoreFoundation 0x00007fff8bfba272 ___forwarding___ + 1010
4 CoreFoundation 0x00007fff8bfb9df8 _CF_forwarding_prep_0 + 120
5 FinderExt 0x000000010835b1f7 -[NSImageView(IconOverlayHandlers) IconOverlayHandlers_drawRect:] + 256
6 AppKit 0x00007fff932f1557 -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inGraphicsContext:CGContext:topView:shouldChangeFontReferenceColor:] + 1082
7 AppKit 0x00007fff932f1890 -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inGraphicsContext:CGContext:topView:shouldChangeFontReferenceColor:] + 1907
8 AppKit 0x00007fff932f100d __46-[NSView(NSLayerKitGlue) drawLayer:inContext:]_block_invoke + 186
9 AppKit 0x00007fff932f0e03 -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 2297
10 AppKit 0x00007fff932f04f8 -[NSView(NSLayerKitGlue) drawLayer:inContext:] + 108
11 QuartzCore 0x00007fff8cd94812 CABackingStoreUpdate_ + 2220
12 QuartzCore 0x00007fff8cd93f60 ___ZN2CA5Layer8display_Ev_block_invoke + 59
13 QuartzCore 0x00007fff8cd93f1c x_blame_allocations + 84
14 QuartzCore 0x00007fff8cd93a2b _ZN2CA5Layer8display_Ev + 1539
15 AppKit 0x00007fff932f03c3 _NSBackingLayerDisplay + 235
16 AppKit 0x00007fff932c774b -[_NSViewBackingLayer display] + 811
17 QuartzCore 0x00007fff8cd93162 _ZN2CA5Layer17display_if_neededEPNS_11TransactionE + 590
18 QuartzCore 0x00007fff8cd928b1 _ZN2CA5Layer28layout_and_display_if_neededEPNS_11TransactionE + 35
19 QuartzCore 0x00007fff8cd9233c _ZN2CA7Context18commit_transactionEPNS_11TransactionE + 236
20 QuartzCore 0x00007fff8cd91fd6 _ZN2CA11Transaction6commitEv + 388
21 QuartzCore 0x00007fff8cda2761 _ZN2CA11Transaction17observer_callbackEP19__CFRunLoopObservermPv + 71
22 CoreFoundation 0x00007fff8bf8cd67 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
23 CoreFoundation 0x00007fff8bf8ccd7 __CFRunLoopDoObservers + 391
24 CoreFoundation 0x00007fff8bf7de94 CFRunLoopRunSpecific + 340
25 HIToolbox 0x00007fff92d68a0d RunCurrentEventLoopInMode + 226
26 HIToolbox 0x00007fff92d687b7 ReceiveNextEventCommon + 479
27 HIToolbox 0x00007fff92d685bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
28 AppKit 0x00007fff9319024e _DPSNextEvent + 1434
29 AppKit 0x00007fff9318f89b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
30 AppKit 0x00007fff9318399c -[NSApplication run] + 553
31 AppKit 0x00007fff9316e783 NSApplicationMain + 940
32 Finder 0x0000000107cb8730 Finder + 26416
33 libdyld.dylib 0x00007fff8c6655fd start + 1
34 ??? 0x0000000000000001 0x0 + 1
)

 

[magnamaduin]

So here is some more specific behavior of the glitch:

NOT ALL folders are affected by the bug. The top level folder of every hard drive except the boot drive work normally. Their subfolders remain glitched.

Some folders accessible by the Finder's Go menu functions normally, even when you navigate to them without using the Go menu. There are: Find, Home and Applications. As above, their subfolders do glitch.

(Desktop, Documents, Downloads, Utilities, Network, Computer and Airdrop all glitch.)

Dejanire and qwerty123, can you replicate my findings? I'm talking both this behavior and the junk in the Console.

 

[magnamaduin]

The problem is Google Drive.

In a working system, launching Google Drive starts the Core Animation problem.

It was probably occurring shortly after Finder relaunch due to Google Drive being in your startup items.

While there is no changelog for Google Drive on March 12, something must have happened.

SOLUTION: Quit Google Drive, then relaunch the Finder. Everything will be fine then.

 

[malkus]

The problem is Google Drive.

SOLUTION: Quit Google Drive, then relaunch the Finder. Everything will be fine then.

I can confirm that this will indeed fix the problem. So I guess we'll just have to wait for a fix from either Apple or Google. Frustrating as I rely on Drive quite a lot.

Considering that there hasn't really been any worldwide outcry regarding this, there might be some specific software conflict involved in our specific cases. Any thoughts?

 

[magnamaduin]

After jiggering around with Google Drive's present functionality, I discovered that "pausing" it in its menu and then relaunching the Finder had the same effect as quitting Google Drive and relaunching the Finder.

This suggests to me that the problem is happening with one of Google Drives processes that results in a Core Animation call.

So I delved deeper into Google Drive's preferences looking for things that could trigger visual reactions in the Finder.

In the Advanced tab of the Google Drive preferences, I unckecked the box for "Show file sync status icons and right click menu" and unpaused Google Drive. The Finder error came back after a minute, as is its custom.

I went back and unchecked the next option, "Show confirmation when removing items from shared folders." and relaunched the Finder while leaving Google Drive unpaused. In testing, this resulted in more than 10 minutes of stability.

I then tried rechecking "Show file sync status icons and right click menu" to test if the problem was just the other feature, and that was not the case (I even got a legitimate Finder crash for my trouble). I was able to verify that unckecking both options keeps Core Animation happy, though I've yet to double down and return Google Drive to my startup items.

 

[eravisz]

I got through the same problem, it has been fixed by quitting Google Drive and relaunching Finder . thank you Magnamaduin !