Finder Keeps Closing (Crashing)

Question

Level 1

0 points

Finder Keeps Closing (Crashing)

Each time I open the finder window, and viewing the file info, normally on the third file the finder closes. it will also close if I'm opening files, normally again after opening 3-4 files. I have tried deleting the com.apple.finder.plist & com.apple.sidebarlists.plist. But the problem still persist.

Anyone got any ideas?

MacBook, Mac OS X (10.4.9)

Posted on May 18, 2007 12:13 PM

Reply

Answer 1

May 18, 2007 12:29 PM in response to Al's

Use the Console application from /Applications/Utilities to examine the console.log and system.log to see if there is mention of a Finder.crash.log being written. If so. open it in Console (you can use the "Logs" button) and see what it says. It will be under ~/Library/Logs/CrashReporter.

The log is cumulative: a new section is added each time the Finder crashes. It should give you a clue why this is happening.

Reply

Answer 2

Al's Author

Level 1

0 points

May 18, 2007 1:39 PM in response to Michael Conniff

Michael I did as suggested. I found the finder crash log and mark from the last report. The finder crash and added to the bottom of the log. Very large report and it made little sense to me I'm afraid. Here is the very top section, there is much much more..... any ideas?? it always happens after checking the file info on the 3rd files!!
__________________________________________________________
Date/Time: 2007-05-19 00:23:16.333 +0400
OS Version: 10.4.9 (Build 8P2137)
Report Version: 4

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

Version: 10.4.7 (10.4.7)
Build Version: 2
Project Name: Finder_FE
Source Version: 5292900

PID: 543
Thread: 0

Exception: EXC BADACCESS (0x0001)
Codes: KERN PROTECTIONFAILURE (0x0002) at 0x00000028

Thread 0 Crashed:
0 libobjc.A.dylib 0x90a594c7 objc_msgSend + 23
1 com.apple.HIToolbox 0x92ec3ea2 InsertMenuItemTextWithCFString + 68
2 com.apple.HIToolbox 0x92ecded0 TPluginMenuItemHandler::AddCommandsToMenu(TPluginCommandList&, OpaqueMenuRef*, unsigned short, TMenuAllocator&) + 376
3 com.apple.HIToolbox 0x92ecde33 TPluginMenuItemHandler::AddCommandsToMenu(TPluginCommandList&, OpaqueMenuRef*, unsigned short, TMenuAllocator&) + 219
4 com.apple.HIToolbox 0x92ecdcae TPluginMenuItemHandler::TPluginMenuItemHandler[in-charge](TPluginCommandList&, OpaqueMenuRef*, TMenuAllocator&) + 158
5 com.apple.HIToolbox 0x92eccccb ContextualMenuInsertItems(MenuData*, unsigned short, AEDesc const*, ContextualMenuHelp const*, unsigned long*, OpaqueContextualMenuItemsRef**) + 545
6 com.apple.HIToolbox 0x92ecc737 ContextualMenuSelect + 425
7 com.apple.finder 0x00088d78 0x1000 + 556408
8 com.apple.finder 0x0008f169 0x1000 + 581993
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 0x92de8537 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093
16 com.apple.HIToolbox 0x92de7bdc SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
17 com.apple.HIToolbox 0x92deefbc SendEventToEventTarget + 56
18 com.apple.HIToolbox 0x92e86d6f HIView::Click(OpaqueEventRef*) + 329
19 com.apple.HIToolbox 0x92e86bab HandleClickAsHIView + 145
20 com.apple.HIToolbox 0x92e86531 HandleWindowClick + 507
21 com.apple.HIToolbox 0x92e85fde HandleMouseEvent + 895
22 com.apple.HIToolbox 0x92e2e488 StandardWindowEventHandler + 86
23 com.apple.HIToolbox 0x92de8537 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093
24 com.apple.HIToolbox 0x92de7bdc SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
25 com.apple.HIToolbox 0x92e2ae48 CallNextEventHandler + 62
26 com.apple.finder 0x0001b163 0x1000 + 106851
27 com.apple.finder 0x00108080 0x1000 + 1077376
28 com.apple.finder 0x000779ca 0x1000 + 485834
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 0x92de8537 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093
35 com.apple.HIToolbox 0x92de7bdc SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
36 com.apple.HIToolbox 0x92deefbc SendEventToEventTarget + 56
37 com.apple.HIToolbox 0x92def44f ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 1169
38 com.apple.HIToolbox 0x92de88ee DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2044
39 com.apple.HIToolbox 0x92de7bdc SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
40 com.apple.HIToolbox 0x92deefbc SendEventToEventTarget + 56
41 com.apple.HIToolbox 0x92e32eb3 ToolboxEventDispatcher + 81
42 com.apple.HIToolbox 0x92e318cb 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

Reply

Answer 3

Al's Author

Level 1

0 points

May 18, 2007 2:34 PM in response to Al's

Discovered it was Stuffit. The same problem was on a total of three MAC's 2 x MacBooks and 1 x iMac. If anyone else has the same problem, you will need to COMPLETELY remove Stuffit. NukeStuffitMac (link Below) to take care of this.

ftp://ftp.smithmicro.com/mac/NukeStuffitMacV2.3.app.zip#NukeStuffitMac

Reply

Answer 4

May 18, 2007 3:27 PM in response to Al's

Hi again

Here is the very top section, there is much much more..... any ideas??

Well that is an interesting log, since the Finder seems to have got itself in a loop. I hope you sent this to Apple if it gave you the opportunity.

It looks to me as if you were using the contextual menu to do your "Get Info", rather than from the Finder's File menu or with Command-I. Am I right?

I get very similar crashes from Dock when I use the contextual menu to select a folder and display its content. I usually send the crash report off to Apple, although it doesn't always automatically offer this. There does seem to be a persistent problem with contextual menus.

But then you say

Discovered it was Stuffit.

How did you find this out?

Reply

Answer 5

rodi

Level 1

0 points

May 19, 2007 3:35 AM in response to Al's

I am having essentially the same problem: though mine first began when I would attempt to access particular folders in my Music section. I have used both the menu and the command I to get info; that does not seem to make a difference. Though it began with particular folders, sometimes now I cannot even open finder- it crashes and repeatedly attempts to re-open.

I tried the stuffit removal and still no dice.

My console log says (repeatedly):
terminate called after throwing an instance of 'IAException'
terminate called after throwing an instance of 'IAException'
terminate called after throwing an instance of 'IAException'
2007-05-19 13:28:57.691 SyndicationAgent[311] WARNING: BestCalendarDateFromString - can't interpret: 'Sat 19 May 2007 01:43:37 -800'
2007-05-19 13:28:57.782 SyndicationAgent[311] WARNING: BestCalendarDateFromString - can't interpret: 'Sat 19 May 2007 01:43:37 -800'

Reply

Answer 6

May 19, 2007 9:57 AM in response to rodi

rodi

Welcome to Apple Discussions!!

terminate called after throwing an instance of 'IAException'

Never seen this before. Can you put the message into context? What were you doing? and what comes immediately before and after in the log?

BestCalendarDateFromString - can't interpret:

Several others have had this, and it turned out to be due to a "StuffItCM.plugin" file in "/Library/Contextual Menu Items/". If you have this file, try removing it from that folder and restarting. I know you said "I tried the stuffit removal and still no dice", but please check for this particular file anyway.

Others have reported that it is due to an RSS feed sending a date in a format the system doesn't recognise. If you find the RSS feed and get rid of it, the message should go away.

( Note: Charles Minow has also posted "If you use Safari and haven't cleared the various iTunes Store RSS feeds from its bookmarks, you'll get this error, even though you might never look at them. It's really a problem with the feed and nothing on your Mac. Specifically, it's missing a comma after the day name.")

If either of these fixes your problem, please post back and say which, so others may benefit from the fix.

Reply

Answer 7

yogidig

Level 1

25 points

May 19, 2007 6:17 PM in response to Michael Conniff

Hi, thanx for pointing me in the right direction. It was actually a Stuffit Deluxe 11.0.2 issue. I removed the "StuffItCM.plugin" file in "/Library/Contextual Menu Items/" as you mentioned, I restarted my Mac and everything was working as it should, however, I checked in the stuffit home page (www.stuffit.com) and found a fix for this problem, I tested and works just fine, and I still have my stuffit contextual menu. If you follow the link listed below you should be able to get the fix (it is free access, only works if you have stuffit deluxe 11.0.2 installed)

http://www.stuffit.com/mac/deluxe/StuffItCM11.0.2.628Updater.sitx

Reply

Answer 8

rodi

Level 1

0 points

Jun 8, 2007 2:34 AM in response to Michael Conniff

Hi Michael,

Thanks for the tips. I went into "contextual menu items" and found it blank (I had used the "Stuff it Nuker" earlier proposed.

I don't use Safari nor RSS feeds nonetheless I followed the other tip and deleted all references to Itunes in my RSS feeds.

I really am not doing anything before and after that message. After the RSS deletes, I cleared my log then restarted and now cannot even open Finder- it immediately 'slams' shut, giving the same error message. Yet, I can "cheat" by opening a folder shortcut- if that makes any sense. Neverless, once I go further into sub-folders, eventually Finder slams shut again.

It does seem to be centred around Itunes- when it first began to happen I was sorting my (leaglly bought!) music when I could not access certain folders (by artist). However, as I don't have as elaborate a file structure (folders/ subfolders) with anything else on my computer so its hard to say if it is specfic to Itunes or something linked with going through levels of subfolders.

Any thoughts? Much appreciated.

Reply

Answer 9

Jun 8, 2007 11:05 AM in response to rodi

rodi

Surprised to see you back!

I really am not doing anything before and after that message.

By "that message" I take it you mean:

terminate called after throwing an instance of 'IAException'

Earlier you said you were getting this repeatedly—did you mean once for each time the Finder quits, or several times?

As I said previously, I haven't come across this message. I just spent some time hunting for "IAException" in my system, with no luck, If you are convinced it has something to do with iTunes, you could try posting in that forum with "IAException" in the Topic title to see if anyone recognises it.

Reply

Answer 10

rodi

Level 1

0 points

Jun 8, 2007 11:12 AM in response to Michael Conniff

Hi, sorry for the silence before- poor connections etc.

Suggesting it was related to the music folder was premature, I played around some more and it became with everything.

Yes- when it crashes and I check the console log, I get that message (terminate called after throwing an instance of 'IAException') several times in a row.

Reply

Answer 11

Jun 8, 2007 11:25 AM in response to rodi

rodi

Well it turns out that 'IAException' is a Java thing, for runtime arithmetic exceptions. The only references I can find to that specific error are in German and Spanish (Portuguese?):
MacTechNews.de - News Tag und Nacht
MacTechNews.de - News Tag und Nacht (2)
Problema al leer unidad de red - Comunidad Macuarium.

I don't know where to go further with this since I don't speak either language. But maybe you should reinstall Java?

Reply

Answer 12

rodi

Level 1

0 points

Jun 9, 2007 4:47 AM in response to Michael Conniff

Hi again Michael,

I bought my Macbook Pro already load so am not sure if I have access to a copy of Java. Somewhere I have one CD which came with it but cannot seem to track that down.

Looking back at the error message,

"BestCalendarDateFromString - can't interpret: 'Sat 19 May 2007 01:43:37 -800'"

and considering what you said about it essentially looping itself, I wonder if there is something with my date or calendar? I don't have any advance setup though.

Thanks for all the advice by the way.

Reply

Answer 13

Jun 9, 2007 10:15 AM in response to rodi

rodi

I bought my Macbook Pro …

Wait a minute … which machine are we talking about here? Your current profile shows "IBook G4 Mac OS X (10.3)" although your first post showed "Macbook Pro Mac OS X (10.4.9)". I'll assume the latter …

On "BestCalendarDateFromString …" note what I posted above:

(Note: Charles Minow has also posted "If you use Safari and haven't cleared the various iTunes Store RSS feeds from its bookmarks, you'll get this error, even though you might never look at them. It's really a problem with the feed and nothing on your Mac. Specifically, it's missing a comma after the day name.")

So I'm not sure what you can do about this except go through your Safari bookmarks and delete any that refer to the iTunes store.

Now to Java. You will have it, so let's check the version. Open the Terminal (from /Applications/Utilities) and copy and paste the following into the Terminal window, one line at a time, followed by a return:

java -version

My output from this shows:

java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164)
Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode)

Then also try pasting this:

ls -al /usr/bin/java

and post what you get.

Reply

Answer 14

rodi

Level 1

0 points

Jun 10, 2007 2:28 AM in response to Michael Conniff

Hi Michael,

Sorry, never thought to update my profile. Will do. I previsouly did clear Safari bookmarks, BTW (see a couple posts back- I don't use Safari nor RSS).

I will try the procedure you recommend when I get home from work. Does it have me actually removing Java and if so- will I need the install disc at hand? Reason I ask is that I'm shuffling around these days and would have some serious box-searching to do!

Best,

Rod

Reply

Answer 15

Jun 10, 2007 9:24 AM in response to rodi

rodi

Your profile is only important in that the version of Java may be different for 10.3 and 10.4, so be sure to confirm we are talking about Tiger.

I don't use Safari nor RSS

Well, that's the only source of these errors that I currently know about. The errors are mainly harmless, but could cause problems if they start filling your log files quickly.

Does it have me actually removing Java

No, the commands will tell me which version of Java you have installed, and its date.

Reply

Quick Links

Finder Keeps Closing (Crashing)