[archdukefranz]

Amsn and Fire won't display then stop responding... (Never tried either of these apps before)
And dreamweaver has been doing the same...

How do I find out whats going on with these apps?
Is there some utility of crash log?

Sorry if this is the wrong place for this, I'm new to the forum and this seemed like the best place?

[siMac]

You can open Console.app (in Applications/Utilities) to see the crash logs. Try repairing permissions in Disk Utility.

[peeb]

Can you say a little more? What machine? You say they never worked - does this happen with other apps? Did Dreamweaver work before? Has anything changed about your settup?

[archdukefranz]

Originally Posted by peeb 

Can you say a little more? What machine? You say they never worked - does this happen with other apps? Did Dreamweaver work before? Has anything changed about your settup?

OK its a 17inch MBP 2.13 Core 2 Duo

Recently had the HDD replaced... some programs were crashing and eventually everything died...
Sent into applecare and they fixed it.

Ok during a time of greater patience I let the programs run a little longer and it just turned out they were taking forever to do anything.
Whenever I hover my mouse over amsn it gives me the spirally waiting cursor for ages.. then eventually it can do another operation which I have to wait for...

Same thing happens with dreamweaver only to a lesser extent...
Happened with fetch too... an ftp program.

Had a look at console.app but it didn't seem to come up with anything at all since boottime

Verified disk perms and it came up with some macromedia support thing which had read write execute for everyone and shouldn't
hardly the problem I'm sure...

Did a disk verify too.. it passed...

[archdukefranz]

Arg now dreamweaver is crashing regularly... I'm really confused as to whats causing all this

[frankthetank966]

My suggestion is get the Mac OS X CD Disc 1. Insert that into your console while the computer is on. Turn off the computer and when you reboot it, hold down the "C" key until the widget (windmill) begins to spin. Since I am doing this off the top of my head I do not know the exact words. Push continue to get onto the cd. Then on the top left go to "utilities">"disk utility". When you are in Disk Utility go to your Macintosh Hard Drive and select repair disk. After it successfully repairs the disk restart the computer but make sure you take out the cd. Good Luck

[archdukefranz]

Here is the crash report on dreamweaver... it won't open now...

Date/Time: 2007-02-08 10:23:53.654 +0000
OS Version: 10.4.8 (Build 8N1037)
Report Version: 4

Command: Dreamweaver
Path: /Applications/Macromedia Dreamweaver 8/Dreamweaver 8/Contents/MacOS/Dreamweaver
Parent: WindowServer [56]
Rosetta: Yes

Version: 8.0.0.2734 (8.0.0)

PID: 2576
Thread: Unknown

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

Thread 0:
0 com.macromedia.Dreamweaver 0xb80a5453 0xb8000000 + 676947
1 com.macromedia.Dreamweaver 0xb809f925 0xb8000000 + 653605
2 com.macromedia.Dreamweaver 0xb80bd24e 0xb8000000 + 774734
3 com.macromedia.Dreamweaver 0xb811de0d spin_lock_wrapper + 1985

Thread 1:
0 com.macromedia.Dreamweaver 0xb823369b strchr + 72
1 com.macromedia.Dreamweaver 0xb81cef17 pthread_cond_wait + 3114
2 com.macromedia.Dreamweaver 0xb816831a catch_exception_raise_state_identity + 318
3 com.macromedia.Dreamweaver 0xb8167856 CallPPCFunctionAtAddressInt + 177220
4 com.macromedia.Dreamweaver 0xb816774d CallPPCFunctionAtAddressInt + 176955
5 com.macromedia.Dreamweaver 0xb8168418 catch_exception_raise_state_identity + 572
6 com.macromedia.Dreamweaver 0xb820480c pthread_create + 1124

Thread 2:
0 com.macromedia.Dreamweaver 0xb813501e spin_lock_wrapper + 96722
1 com.macromedia.Dreamweaver 0xb814e1b4 CallPPCFunctionAtAddressInt + 73122
2 com.macromedia.Dreamweaver 0xb80c7b3a 0xb8000000 + 817978

Thread 3:
0 com.macromedia.Dreamweaver 0xb81352b4 spin_lock_wrapper + 97384
1 com.macromedia.Dreamweaver 0xb8148d85 CallPPCFunctionAtAddressInt + 51571
2 com.macromedia.Dreamweaver 0xb80a6073 0xb8000000 + 680051
3 com.macromedia.Dreamweaver 0xb809f925 0xb8000000 + 653605
4 com.macromedia.Dreamweaver 0xb80bd24e 0xb8000000 + 774734
5 com.macromedia.Dreamweaver 0xb811e558 spin_lock_wrapper + 3852

Thread 4:
0 com.macromedia.Dreamweaver 0xb8134fac spin_lock_wrapper + 96608
1 com.macromedia.Dreamweaver 0xb814dfdc CallPPCFunctionAtAddressInt + 72650
2 com.macromedia.Dreamweaver 0xb80a6073 0xb8000000 + 680051
3 com.macromedia.Dreamweaver 0xb809f925 0xb8000000 + 653605
4 com.macromedia.Dreamweaver 0xb80bd24e 0xb8000000 + 774734
5 com.macromedia.Dreamweaver 0xb811e558 spin_lock_wrapper + 3852

Thread 5:
0 com.macromedia.Dreamweaver 0xb813501e spin_lock_wrapper + 96722
1 com.macromedia.Dreamweaver 0xb814e1b4 CallPPCFunctionAtAddressInt + 73122
2 com.macromedia.Dreamweaver 0xb80c7b3a 0xb8000000 + 817978

Thread 6:
0 com.macromedia.Dreamweaver 0xb813501e spin_lock_wrapper + 96722
1 com.macromedia.Dreamweaver 0xb814e1b4 CallPPCFunctionAtAddressInt + 73122
2 com.macromedia.Dreamweaver 0xb80c7b3a 0xb8000000 + 817978

Unknown thread crashed with unknown flavor: 1
state_count: 16

[seanc]

RAM. Have you added any recently? Take out one of the sticks (assuming you have two) and try running then, swap the one you took out for the one still in there if it's still crashing. If that still doesn't work, try the originals that came with the computer.

[glypht]

As far as I know Dreamweaver isn't universal yet which is probably why it's responding slowly and possibly why it's crashing too. As for aMSN it's an open source project so maybe there'll be an update soon, or maybe there are nightlies available.

Are there any other apps crashing systematically or is it just those two?

[Old Toad]

Try deleting the Dreamweaver preference file.

[Thinine]

May be a problem with Rosetta. Are you using the Universal version of Fetch?

[raduga]

The title of this thread reminds me of an old joke...

Most
Applications
Crash
If
Not,
The
Operating
System
Hangs

[peeb]

Well this isn't normal - are you near an apple store? Try taking it in to them.

[frankthetank966]

Did you repair the disk yet?