[grayware]

I keep getting Finder crashes, and here's the last log. Looks like Shapeshifter, but I love it, so what do you recommend to get past this? Make a new user? Reinstall SS? Archive and reinstall OS?

Date/Time: 2005-05-30 22:46:04 -0400
OS Version: 10.3.9 (Build 7W98)
Report Version: 2

Command: Finder
Path: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
Version: 10.3.2 (10.3.2)
PID: 218
Thread: 0

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

Thread 0 Crashed:
0 com.apple.finder 0x00060b00 0x1000 + 0x5fb00
1 com.apple.finder 0x00051430 0x1000 + 0x50430
2 com.apple.finder 0x000506ac 0x1000 + 0x4f6ac
3 com.apple.finder 0x0004fe14 0x1000 + 0x4ee14
4 com.apple.finder 0x0009fd34 0x1000 + 0x9ed34
5 com.apple.finder 0x001015d8 0x1000 + 0x1005d8
6 com.apple.finder 0x00100f6c 0x1000 + 0xfff6c
7 com.apple.finder 0x0018ab64 0x1000 + 0x189b64
8 com.apple.finder 0x0018a850 0x1000 + 0x189850
9 com.apple.finder 0x000fe55c 0x1000 + 0xfd55c
10 com.apple.finder 0x000fc5bc 0x1000 + 0xfb5bc
11 com.apple.finder 0x0003ae00 0x1000 + 0x39e00
12 com.apple.finder 0x0003e798 0x1000 + 0x3d798
13 com.apple.finder 0x0005de24 0x1000 + 0x5ce24
14 com.apple.finder 0x0005dc4c 0x1000 + 0x5cc4c
15 com.apple.finder 0x0002c1bc 0x1000 + 0x2b1bc
16 com.apple.finder 0x0005b17c 0x1000 + 0x5a17c
17 com.apple.finder 0x0005ad28 0x1000 + 0x59d28
18 com.apple.finder 0x0005aa1c 0x1000 + 0x59a1c
19 com.apple.finder 0x0000f954 0x1000 + 0xe954
20 com.apple.finder 0x0000dad0 0x1000 + 0xcad0
21 com.apple.finder 0x0000a078 0x1000 + 0x9078
22 com.apple.finder 0x0000ca54 0x1000 + 0xba54
23 <<00000000>> 0x92881fa0 0 + 0x92881fa0
24 <<00000000>> 0x92882214 0 + 0x92882214
25 <<00000000>> 0x928946bc 0 + 0x928946bc
26 <<00000000>> 0x928a2d3c 0 + 0x928a2d3c
27 <<00000000>> 0x929c3524 0 + 0x929c3524
28 <<00000000>> 0x92892c5c 0 + 0x92892c5c
29 <<00000000>> 0x9288205c 0 + 0x9288205c
30 <<00000000>> 0x92882214 0 + 0x92882214
31 <<00000000>> 0x928946bc 0 + 0x928946bc
32 <<00000000>> 0x928985d8 0 + 0x928985d8
33 <<00000000>> 0x928b57e4 0 + 0x928b57e4
34 <<00000000>> 0x928ab680 0 + 0x928ab680
35 com.apple.finder 0x00035630 0x1000 + 0x34630
36 com.apple.finder 0x00033f28 0x1000 + 0x32f28
37 com.apple.finder 0x00032fd4 0x1000 + 0x31fd4
38 com.apple.finder 0x00032e48 0x1000 + 0x31e48

Thread 1:
0 libSystem.B.dylib 0x90007878 mach_msg_trap + 0x8
1 libSystem.B.dylib 0x900073f8 mach_msg + 0x38
2 com.unsanity.ape 0xc0002bf4 __ape_internal + 0xce4
3 com.unsanity.ape 0xc0001a08 __ape_agent + 0x40
4 libSystem.B.dylib 0x90024910 _pthread_body + 0x28

Thread 2:
0 libSystem.B.dylib 0x90018e18 semaphore_timedwait_signal_trap + 0x8
1 libSystem.B.dylib 0x9000e9d4 _pthread_cond_wait + 0x268
2 <<00000000>> 0x902c5a50 0 + 0x902c5a50
3 <<00000000>> 0x90948e7c 0 + 0x90948e7c
4 <<00000000>> 0x902f6b90 0 + 0x902f6b90
5 libSystem.B.dylib 0x90024910 _pthread_body + 0x28

PPC Thread State:
srr0: 0x00060b00 srr1: 0x0200f030 vrsave: 0x00000000
cr: 0x24824444 xer: 0x20000006 lr: 0x00051430 ctr: 0x0003c40c
r0: 0x00000001 r1: 0xbfffea60 r2: 0x00000000 r3: 0x018f4200
r4: 0xbfffeb60 r5: 0x00000000 r6: 0xa01c0dcc r7: 0xa01c0dcc
r8: 0xa01c0dcc r9: 0x00600fe0 r10: 0x00000000 r11: 0x24824444
r12: 0x0003c40c r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000002 r21: 0x00000030 r22: 0x00000001 r23: 0x00000001
r24: 0x72676874 r25: 0x646e616d r26: 0x69636e76 r27: 0xbfffecd0
r28: 0x018f4330 r29: 0xbfffeb60 r30: 0x018f43c8 r31: 0x018f4200

Binary Images Description:
0x1000 - 0x29ffff com.apple.finder 10.3.2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
0x1008000 - 0x102dfff com.unsanity.shapeshifter ShapeShifter Version 2.1 (2.1) /Users/jholden/Library/Application Enhancers/ShapeShifter.ape/Contents/MacOS/ShapeShifter
0x12f1000 - 0x12f3fff com.apple.textencoding.unicode 1.6.4 /System/Library/TextEncodings/Unicode Encodings.bundle/Contents/MacOS/Unicode Encodings
0x80830000 - 0x8090efff libxml2.2.dylib /usr/lib/libxml2.2.dylib
0x82410000 - 0x824d9fff com.apple.PowerPlant 1.0.3 /System/Library/PrivateFrameworks/PowerPlant.framework/Versions/A/PowerPlant
0x8fe00000 - 0x8fe4ffff dyld /usr/lib/dyld
0x90000000 - 0x9014ffff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0xc0000000 - 0xc000ffff com.unsanity.ape 1.5 /Library/Frameworks/ApplicationEnhancer.framework/Versions/A/ApplicationEnhancer

[Randman]

Search for Finder and trash the plist file. Empty trash. Repair permissions, log off and back on.

[mportuesi]

I think I saw somewhere that the makers of ShapeShifter have put out a Tiger update. Perhaps you should check with them.

Personally, I'd get rid of ShapeShifter. I don't see the logic in buying a system that is known for stability, then making it unstable by installing haxies and other "customizations" that simply get in the way of the OS.

[Randman]

SS is very stable.

[esXXI]

ShapeShifter appears in crashes regardless, because it's in use by the application. Just because it's log doesn't mean it's the cause.

@mportuesi: What proof have you got that ShapeShifter is unstable? I've yet to read about any wide spread crashes (or even problems) even on forums where most users are using it.

[mportuesi]

Originally Posted by esXXI

@mportuesi: What proof have you got that ShapeShifter is unstable?

I have no proof. It's simply one more thing on your system that can/will break when a system update arrives.

Generally I try to avoid customization software unless there's a really compelling benefit it provides beyond eye candy. I find my system is more stable that way.

[Randman]

Originally Posted by mportuesi

I have no proof. It's simply one more thing on your system that can/will break when a system update arrives.

You have no proof but you post that it's unstable.

Anything can break on a system update.

[mportuesi]

Originally Posted by Randman

Anything can break on a system update.

Exactly. That's why the fewer things you have, the fewer things will break. Especially for things that are "on all the time" and affect system behavior across the board, rather than apps that run only when you launch them, and don't affect the system as a whole.

Having used a Mac for over two years, I've never had a problem with a system update. I've never had to trash plist files, repair permissions, or any of the other "witch doctor" things Mac owners do to fix glitchy systems. One big reason is because I don't put any "customization" software on my system in the first place.

[Randman]

Then you shouldn't spread FUD unless you have a link or first-hand experience detailing problems before posting that something is unstable.

[mportuesi]

Originally Posted by Randman

Then you shouldn't spread FUD unless you have a link or first-hand experience detailing problems before posting that something is unstable.

I'm not spreading FUD. Shapeshifter was listed in the crash dump, and the maker has issued a Tiger compatibility update:

ShapeShifter 2.1:

(http://www.unsanity.com/haxies/shapeshifter/)

Tiger compatibility is the first bullet point for the update.

I don't know if SS is stable or not. But it sure sounds like the Tiger update broke it.

[smeger]

grayware isn't running Tiger, and as Randman correctly points out, ShapeShifter will always be present in a crashlog if it's installed. Present != causal.

grayware, if you think it might be ShapeShifter, use the APE Manager preference pane to disable ShapeShifter and then log out and back in. If the problems persist, it's something else. I'm not aware of any ShapeShifter problems with 10.3.9, so I suspect it's probably something else.

The usual culprit for mysterious Finder crashes is a corrupted file that Finder is trying to generate a preview for. You might try moving any files on your desktop to a folder that's tucked away somewhere to see if that resolves it. Or, see whether you can correlate opening a particular folder with a crash.

Deleting <your home directory>/Library/Preferences/com.apple.finder.plist is also a good idea.

[dru]

Originally Posted by mportuesi

I have no proof. It's simply one more thing on your system that can/will break when a system update arrives.

By that logic you shouldn't run anything at all!

I've been running haxies for years and haven't noticed any stability problems. The only thing that falls over for me is the Finder (haxies or none) which has been much more stable on Tiger than any prior release.

If you have no evidence, best to keep to yourself rather than slander a company's product on an open forum.

(This isn't Windows or the Classic MacOS which definitely, demonstrably, suffer from having too many little things loading by default.)