Screen switching, finder crash.

Question

I&#x27;ve been looking around to try to find a solution but so far I haven&#x27;t found anyone that had my exact issue. First my problem was that when using Chrome maximized (what i mean here is that it was in the second screen that you access with the three finger slide gesture) the screen would keep switching back to screen one (the screen with the dock). I thought this was the only problem, but then I opened finder and found that it would keep closing and then would pop back up a few seconds later.

Linc Davis · Answer

Launch the Console application in any of the following ways:☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens. ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.Step 1Make sure the title of the Console window is All Messages. If it isn&#x27;t, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don&#x27;t see that menu, selectView ▹ Show Log Listfrom the menu bar.Enter the name of the crashed application or process in the Filter text field. Select the messages from the time of the last crash, if any. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.Please do not indiscriminately dump thousands of lines from the log into this discussion.Important: Some private information, such as your name, may appear in the log. Anonymize before posting.Step 2In the Console window, look under User Diagnostic Reports for crash reports related to the crashed process. The report name starts with the name of the process, and ends with ".crash". Select the most recent report and post the entire contents — again, the text, not a screenshot. In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they&#x27;re very long and not helpful.

AustinofEarth · Answer

Date/Time:       2013-08-27 18:03:57.953 -0700OS Version:      Mac OS X 10.8.4 (12E55)Report Version:  10Sleep/Wake UUID: 59263E85-8365-4F18-A2B2-7D1DA7E92191Crashed Thread:  4Exception Type:  EXC_BAD_ACCESS (SIGSEGV)Exception Codes: KERN_INVALID_ADDRESS at 0x00000001017e91b4External Modification Warnings:Thread creation by external task.VM Regions Near 0x1017e91b4:--&gt;     __TEXT                 0000000105a9f000-0000000105f5a000 [ 4844K] r-x/rwx SM&#x3D;COW  /System/Library/CoreServices/Finder.app/Contents/MacOS/FinderThread 0:: Dispatch queue: com.apple.main-thread0   libsystem_kernel.dylib                  0x000000010b632686 mach_msg_trap + 101   libsystem_kernel.dylib                  0x000000010b631c42 mach_msg + 702   com.apple.CoreFoundation                0x00000001084bb233 __CFRunLoopServiceMachPort + 1953   com.apple.CoreFoundation                0x00000001084c0916 __CFRunLoopRun + 10784   com.apple.CoreFoundation                0x00000001084c00e2 CFRunLoopRunSpecific + 2905   com.apple.HIToolbox                     0x0000000107093eb4 RunCurrentEventLoopInMode + 2096   com.apple.HIToolbox                     0x0000000107093c52 ReceiveNextEventCommon + 3567   com.apple.HIToolbox                     0x0000000107093ae3 BlockUntilNextEventMatchingListInMode + 628   com.apple.AppKit                        0x0000000109034533 _DPSNextEvent + 6859   com.apple.AppKit                        0x0000000109033df2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 12810  com.apple.AppKit                        0x000000010902b1a3 -[NSApplication run] + 51711  com.apple.AppKit                        0x0000000108fcfbd6 NSApplicationMain + 86912  com.apple.finder                        0x0000000105aa4b56 0x105a9f000 + 2338213  libdyld.dylib                           0x000000010b4587e1 start + 1Thread 1:: Dispatch queue: com.apple.libdispatch-manager0   libsystem_kernel.dylib                  0x000000010b634d16 kevent + 101   libdispatch.dylib                       0x000000010b41edea _dispatch_mgr_invoke + 8832   libdispatch.dylib                       0x000000010b41e9ee _dispatch_mgr_thread + 54Thread 2:0   libsystem_kernel.dylib                  0x000000010b6346d6 __workq_kernreturn + 101   libsystem_c.dylib                       0x000000010b4c1f4c _pthread_workq_return + 252   libsystem_c.dylib                       0x000000010b4c1d13 _pthread_wqthread + 4123   libsystem_c.dylib                       0x000000010b4ac1d1 start_wqthread + 13Thread 3:0   libsystem_kernel.dylib                  0x000000010b6346d6 __workq_kernreturn + 101   libsystem_c.dylib                       0x000000010b4c1f4c _pthread_workq_return + 252   libsystem_c.dylib                       0x000000010b4c1d13 _pthread_wqthread + 4123   libsystem_c.dylib                       0x000000010b4ac1d1 start_wqthread + 13Thread 4 Crashed:0   ???                                     0x00000001017e91b4 0 + 4320039348Thread 4 crashed with X86 Thread State (64-bit):  rax: 0x0000000000000000  rbx: 0x0000000000000056  rcx: 0x000000010702f000  rdx: 0x0000000000000056  rdi: 0x000000010702f000  rsi: 0x0000000107033000  rbp: 0x0000000107030ff4  rsp: 0x0000000107030f7c   r8: 0x0000000000000000   r9: 0x0000000000000000  r10: 0x0000000000000000  r11: 0x0000000000000000  r12: 0x0000000000000000  r13: 0x0000000000000000  r14: 0x0000000107033000  r15: 0x0000000000000000  rip: 0x00000001017e91b4  rfl: 0x0000000000010206  cr2: 0x00000001017e91b4Logical CPU: 2

Linc Davis · Answer

That kind of crash is often caused by "Google Drive." If it&#x27;s installed, I suggest you remove it according to the developer&#x27;s instructions. You may need to boot in safe mode to do so. Back up all data before making any changes.