Finder windows randomly closing and reloading!

[FunBoy50]

Whats's going on!??

My finder windows have recently started to randomly close and reload for no reason....

I don't get a 'this has unexpectedly quit' message, but whatever i'm doing in finder closes and reloads back to my mounted volumes...

Is this happening to anyone else? (weird bug) or is it just me?!

 

[tsvb]

Have you changed anything on your system recently?

 

[breakfastcrew]

hey me too my finder windows closes everytime I rename a folder, add a folder or change the contents of somethiing. I am on a macbook and I recently did the efi and smi firmware upgrade.

 

[skoone]

Yep, same thing happening here. Mac Pro computer.. To my knowledge, I haven't changed anything nor have I loaded any new software recently. This random issue started about a week ago. Since then, I find that I can be working in a folder window, doing whatever, and all of a sudden, the window closes up by itself, all icons on the desktop do this sort of "refresh".. They momentarily disappear and then return.. Almost like something crashed and then recovered.

If I had to nail down any specific activity that I'm doing in a window that this issue happens more often than not, it's when I'm moving or copying files from one window to another.

Weird!

 

[FunBoy50]

Skoone my PowerMac G5 does exactly the same as your Mac Pro!

It started about a week ago, when I'm moving, editing or copying stuff in finder, it will unpredictably and sporadically close, my desktop icons disappear, and they load back about a second later.

What is happening? I'm running 10.4.8 with all the latest security updates, so what's going on?!?!?!

 

[breakfastcrew]

help we are kinda screw

 

[ForeverUnknown]

I've been having this issue with my new MacBook Pro! I've been talking to Apple Support about it and they can't figure it out. I've reinstalled and reformatted MANY times over the last week. However for some reason after one more reformat and install last night, things have settled. I don't know what changed, but I hope nothing breaks after this.

Try repairing permissions and disk. Delete plists from your system. At least specifically Finder. Also you can search for the crash log and see what's happening. Just search for "finder crash" in spotlight.

 

[breakfastcrew]

where do I do delete plist? and which ones do I delete? Can I delete all of them?

 

[skoone]

I nabbed a few snippets from my finder.crash log:

Version: 10.4.6 (10.4.6)
Build Version: 8
Project Name: Finder_FE
Source Version: 5292800

PID: 1966
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000028



......and this:

Version: 10.4.6 (10.4.6)
Build Version: 8
Project Name: Finder_FE
Source Version: 5292800

PID: 2027
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xfeffffff


......and another one of these:

Version: 10.4.6 (10.4.6)
Build Version: 8
Project Name: Finder_FE
Source Version: 5292800

PID: 96
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000261

My crashes have become quite frequent now, a major issue for me here.. And it's only related to Finder-type activities.. Other functionality or running other applications are not affected. I have reset PRAM and SMC, no change. I had thought of approaching Apple about this, but since someone else here has already talked to them with no positive results, I'm unsure what to advise at this point. My Mac Pro is loaded software-wise to the point that for me to wipe the drive and start over with a fresh install would be tremendously time consuming.. It simply isn't feasible! There has to be something in common, something that we have all downloaded that is causing this to occur. Could it be a common hardware issue? Has Apple sent us some updated software recently via Software Update that could be causing this? I just find it awfully peculiar that all of a sudden, here we have a select number of us out here confronting the exact same specific problem at pretty much an identical time frame. I have a feeling that we're gonna have to keep beating on Apple about this one as I suspect it has something to do with them.

Steve

 

[breakfastcrew]

since we all have different computers it can't be the system updates. Did any of you guys install the garage band, imovie aperature updates release a few months back?

 

[ForeverUnknown]

skoone: The lines below are actually more important since they give information regarding which process crashed. http://www.macfixit.com/article.php?story=20060309075929717



My MBP is brand new and the only updates I've applied are a couple system updates except for the latest iChat update. To test if it's any 3rd party app causing problems, I reinstalled OS X, updated and only installed Firefox, VLC, and Adium to give me something to do while waiting to see if something crashes, but I still have issues.

Today I installed Office 04, the updater crashed and didn't restart. I looked into the crash log and it looks like that time was a issue with BOMarchiver (not exactly what it's called but I don't have my Mac to check)



I've actually sent my Mac to Apple today which they will receive tomorrow, so I'm curious if my case is anything hardware related. I doubt it but since it's under warranty, why not get this baffling mystery checked out. I've never had issues with my iBook running the same software, so I'm stumped.

 

[FunBoy50]

the worst thing is that i was running 10.4.6 and it started happening.

I didn't like the look of it, so i did a full system re-install. I deleted and re-installed my entire OS and upgraded straight to 10.4.8 with all the latest security. (don't worry all my picture and music files etc are on a separate partition)

I was well not happy when it did the same thing again, and that is on a fresh system!!!

 

[breakfastcrew]

ok I was able to replicate this error by opening a .dmg file and clicking on the contents inside and then injecting it. Usually it happens around 2-3 tries on different .dmg files. Anyone else want to confirm this with me?

 

[ForeverUnknown]

ok I was able to replicate this error by opening a .dmg file and clicking on the contents inside and then injecting it. Usually it happens around 2-3 tries on different .dmg files. Anyone else want to confirm this with me?

My MBP is about to be delivered from Apple so I'll give it a try in a little bit. I know I had problems with unzipping files.

EDIT: The Mac just came in and it looks like they replaced the RAM module. I'm going to reformat and see how things are.

 

[breakfastcrew]

if anyone is curious here is what I updated recently when this problem appeared.


2007-01-05 22:04:25 -0800: Installed "MacBook SMC Firmware Update" (1.1)
2007-01-05 22:09:44 -0800: Installed "MacBook EFI Firmware Update" (1.0)
2007-01-06 16:40:46 -0800: Installed "iMovie HD Update" (6.0.2)
2007-01-06 17:17:59 -0800: Installed "iMovie HD Update" (6.0.3)
2007-01-06 17:18:05 -0800: Installed "GarageBand Update" (3.0.4)
2007-01-06 17:19:01 -0800: Installed "iChat Update (Universal)" (1.0)
2007-01-07 13:43:46 -0800: Installed "Aperture Update" (1.5.2)

 

[breakfastcrew]

bump

 

[ForeverUnknown]

Here are the updates I install:

iTunes 7.0.2
iChat Update (Universal)
Security Update 2006-007 (Intel)
Security Update 2006-008 (Universal)


I had a program, Monaco monitor calibration, crash on me a couple times today, but I think it's because it's a older PPC program. However, Finder did crash on me once today, but I don't remember what I was doing. I repaired permissions and deleted the corresponding plist files, so I hope it fixes it. Ugh headaches. Funny that my Windows machine has been more stable

 

[breakfastcrew]

maybe it is the ichat update. So does anyone think this is a ram problem?? I used my new 2gb ram for a little over a month before this problem appeared.

 

[ForeverUnknown]

Well, Apple tested and swapped out my RAM, so my case could have been a RAM issue.

You can try testing your RAM with Apple Hardware Test that's on the 1st install DVD. Run it in a loop overnight and see if anything pops up.

Oh and try using Preferential Treatment to verify your plist files http://www.jonn8.com/html/pt.html

 

[breakfastcrew]

So did that fix your problem? I ran the hardware test everything passed. I also ran the one from techtool pro and that one passed too. Techtool pro did find some errors with finder and repaired that but the issue is still there.

 

[ForeverUnknown]

So did that fix your problem? I ran the hardware test everything passed. I also ran the one from techtool pro and that one passed too. Techtool pro did find some errors with finder and repaired that but the issue is still there.

I'm not sure yet since my crashes were never consistent, while they do happen at similar events, so I'm simply using my Mac and seeing if anything happens. I've only had one Finder crash today, so things look better.

I'm going to run the Apple Hardware Test all night and see what happens with my RAM. I ran it for a couple hours earlier with no errors, but I'm curious if more time will cause an error. The next night I'm going to run memtest and see what happens with that.

 

[breakfastcrew]

so did the dmg method up above replicate the crash for you? I deleted a whole lot of programs and ran a lot of clean up cache cleaning stuff my problem seems to have decreased but the dmg thing still crashes it.
hmmmm I might have to reinstall osx....sigh the dell m1210 is increasily becoming more attractive than my mac

 

[skoone]

Hi guys..

Still fighting a randomly crashing Finder on my Mac Pro. I have tried removing all of my RAM and re-seating it, I did a re-install of 10.4.8 Combo for intel, I ran preferential treatment, all of my plist files checked fine. I did a disk utility, repaired all permissions. I ran the system check overnight, the computer checked fine.

Something I found rather peculiar while googling for other assistance on this matter:

http://forums.appleinsider.com/archive/index.php/t-29006.html

This is from 2003; another Mac user with a G3 and using OS X 10.2, note that he's having very similar problems as ours! Unfortunately, the guy apparently never fixed his problem or he didn't come back to advise what he did if he managed to fix it. Still seems like about the only viable solution here is to re-install 10.4 and keep on re-installing it until a particular installed copy works. Gee, what a pain for an OS that claims to be so stable. Yeah, I'm also eyeing my dusty PC in the corner.. Perhaps XP wasn't as horrible as I initially thought!

Steve

 

[breakfastcrew]

none of you tested my method yet. I want to see if you guys all have the same problem as me. Can someone plz use the dmg method above to replicate the crash?

o if worst comes to worst we can always wipe os x entirely and use windows on our macs LOL .

 

[ForeverUnknown]

none of you tested my method yet. I want to see if you guys all have the same problem as me. Can someone plz use the dmg method above to replicate the crash?

o if worst comes to worst we can always wipe os x entirely and use windows on our macs LOL .

Doesn't work for me. Finder crashed while right clicking an app then Show Package Contents, but it won't happen again. Here's my crash log below. Looks to be a problem with libobjc.A.dylib or com.apple.HIToolbox, and the address under Exceptions and Codes are the same as my earlier crash.

Command: Finder
Path: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
Parent: WindowServer [643]

Version: 10.4.6 (10.4.6)
Build Version: 16
Project Name: Finder_FE
Source Version: 5292800

PID: 697
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0 Crashed:
0 libobjc.A.dylib 0x90a564c7 objc_msgSend + 23
1 com.apple.HIToolbox 0x92eb4ba2 InsertMenuItemTextWithCFString + 68
2 com.apple.HIToolbox 0x92ebeb50 TPluginMenuItemHandler::AddCommandsToMenu(TPluginCommandList&, OpaqueMenuRef*, unsigned short, TMenuAllocator&) + 376
3 com.apple.HIToolbox 0x92ebeab3 TPluginMenuItemHandler::AddCommandsToMenu(TPluginCommandList&, OpaqueMenuRef*, unsigned short, TMenuAllocator&) + 219
4 com.apple.HIToolbox 0x92ebe92e TPluginMenuItemHandler::TPluginMenuItemHandler[in-charge](TPluginCommandList&, OpaqueMenuRef*, TMenuAllocator&) + 158
5 com.apple.HIToolbox 0x92ebd94b ContextualMenuInsertItems(MenuData*, unsigned short, AEDesc const*, ContextualMenuHelp const*, unsigned long*, OpaqueContextualMenuItemsRef**) + 545
6 com.apple.HIToolbox 0x92ebd3b7 ContextualMenuSelect + 425
7 com.apple.finder 0x00088d08 0x1000 + 556296
8 com.apple.finder 0x0008f0f9 0x1000 + 581881
9 com.apple.finder 0x00066787 0x1000 + 415623
10 com.apple.finder 0x0000d6c9 0x1000 + 50889
11 com.apple.finder 0x0001058b 0x1000 + 62859
12 com.apple.finder 0x0000cec2 0x1000 + 48834
13 com.apple.finder 0x0000ce2a 0x1000 + 48682
14 com.apple.finder 0x0000cdec 0x1000 + 48620
15 com.apple.HIToolbox 0x92dd986b DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093
16 com.apple.HIToolbox 0x92dd8f10 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
17 com.apple.HIToolbox 0x92de01f0 SendEventToEventTarget + 56
18 com.apple.HIToolbox 0x92e77cff HIView::Click(OpaqueEventRef*) + 329
19 com.apple.HIToolbox 0x92e77b3f HandleClickAsHIView + 145
20 com.apple.HIToolbox 0x92e774c5 HandleWindowClick + 507
21 com.apple.HIToolbox 0x92e76f7b HandleMouseEvent + 872
22 com.apple.HIToolbox 0x92e1f6c8 StandardWindowEventHandler + 86
23 com.apple.HIToolbox 0x92dd986b DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093
24 com.apple.HIToolbox 0x92dd8f10 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
25 com.apple.HIToolbox 0x92e1c05c CallNextEventHandler + 62
26 com.apple.finder 0x0001b163 0x1000 + 106851
27 com.apple.finder 0x00108010 0x1000 + 1077264
28 com.apple.finder 0x0007795a 0x1000 + 485722
29 com.apple.finder 0x0001ac68 0x1000 + 105576
30 com.apple.finder 0x0003664d 0x1000 + 218701
31 com.apple.finder 0x0000cec2 0x1000 + 48834
32 com.apple.finder 0x0000ce2a 0x1000 + 48682
33 com.apple.finder 0x0000cdec 0x1000 + 48620
34 com.apple.HIToolbox 0x92dd986b DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093
35 com.apple.HIToolbox 0x92dd8f10 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
36 com.apple.HIToolbox 0x92de01f0 SendEventToEventTarget + 56
37 com.apple.HIToolbox 0x92de0683 ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 1169
38 com.apple.HIToolbox 0x92dd9c22 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2044
39 com.apple.HIToolbox 0x92dd8f10 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
40 com.apple.HIToolbox 0x92de01f0 SendEventToEventTarget + 56
41 com.apple.HIToolbox 0x92e240c7 ToolboxEventDispatcher + 81
42 com.apple.HIToolbox 0x92e22adf RunApplicationEventLoop + 165
43 com.apple.finder 0x00007deb 0x1000 + 28139
44 com.apple.finder 0x00004c6b 0x1000 + 15467
45 com.apple.finder 0x000515b6 0x1000 + 329142
46 com.apple.finder 0x000514dd 0x1000 + 328925

Thread 1:
0 libSystem.B.dylib 0x900268bc kevent + 12
1 ...ple.CoreServices.CarbonCore 0x90cb5f84 PrivateMPEntryPoint + 51
2 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 2:
0 libSystem.B.dylib 0x90024427 semaphore_wait_signal_trap + 7
1 ...ple.CoreServices.CarbonCore 0x90cb6129 MPWaitOnQueue + 198
2 com.apple.DesktopServices 0x9251e943 TNodeSyncTask::SyncTaskProc(void*) + 143
3 ...ple.CoreServices.CarbonCore 0x90cb5f84 PrivateMPEntryPoint + 51
4 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 3:
0 libSystem.B.dylib 0x90048a47 semaphore_timedwait_signal_trap + 7
1 ...ple.CoreServices.CarbonCore 0x90cdf0ab TSWaitOnSemaphoreCommon + 163
2 ...ickTimeComponents.component 0x97ddf18a ReadSchedulerThreadEntryPoint + 4723
3 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 4:
0 libSystem.B.dylib 0x90024427 semaphore_wait_signal_trap + 7
1 com.apple.ColorSync 0x915a5847 pthreadSemaphoreWait(t_pthreadSemaphore*) + 35
2 com.apple.ColorSync 0x915bfdcc CMMConvTask(void*) + 60
3 libSystem.B.dylib 0x90023d87 _pthread_body + 84

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x90810172 ecx: 0x90a639a0 edx: 0x00000000
edi: 0x00000008 esi: 0x0d61b290 ebp: 0xbfffe478 esp: 0xbfffe424
ss: 0x0000001f efl: 0x00010206 eip: 0x90a564c7 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037