continuous crashing after yahoo file xfer

mesenko · Post by **mesenko** » Sat Jul 09, 2005 11:25 pm

A small 20k jpg transfer from yahoo caused my computer to lock up, forcing a hard reboot.

Adium is crashing frequently now.

OS 10.4.1

michael · Post by **michael** » Sat Jul 09, 2005 11:34 pm

File Transfer is extra sucky on Yahoo, although you're under the ~1mb limit so that *shouldn't* be happening...

Post by **jstamos** » Sat Jul 09, 2005 11:43 pm

mesenko wrote:A small 20k jpg transfer from yahoo caused my computer to lock up, forcing a hard reboot.

Adium is crashing frequently now.

OS 10.4.1

Make sure to include your version of Adium when posting.

Post by **Catfish_Man** » Sun Jul 10, 2005 1:06 am

Also Adium shouldn't be capable of causing a system lockup, which makes it particularly interesting. Have you been filing crash reports when possible? (and, as jstamos notes, are you running 0.82?) If so, if you could tell me what email or IM name you filed them as I could have a look and see if I could find out what's causing them (besides the fact that file transfer doesn't work very well).

zaudragon · Post by **zaudragon** » Sun Jul 10, 2005 1:47 am

Catfish_Man wrote:Also Adium shouldn't be capable of causing a system lockup…

Heh. I started a message style, tried opening it in Adium and setting it to the Message Style, and Adium crashed and made me force reboot since the messaqge style didn’t have all of the necessary files…

Post by **The_Tick** » Sun Jul 10, 2005 2:28 am

How did that force a reboot? You couldn't just force kill adium?

mesenko · Post by **mesenko** » Sun Jul 10, 2005 3:42 am

Sorry, version is .82, but since it locked up the computer I couldn't send a crash report. Looked at the console and here's what it reported:

Jul 9 09:46:14 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:46:41 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:47:01 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:47:22 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:47:47 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:48:15 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:48:54 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:49:14 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:50:26 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:50:26 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:50:26 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:50:49 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:51:38 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:52:04 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:52:33 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:53:06 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:53:43 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:54:03 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:54:23 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:55:27 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:56:00 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:56:20 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:56:58 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:58:40 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:59:00 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:59:34 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:59:54 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 10:00:16 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 10:00:36 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 10:01:27 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 10:01:55 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 10:02:15 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 10:03:05 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 10:03:33 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 10:03:53 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 10:04:13 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 10:04:33 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 10:04:54 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 10:05:14 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 10:14:10 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 11:05:35 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 11:05:39 mesenko crashdump[331]: Adium crashed
Jul 9 11:05:42 mesenko crashdump[331]: crash report written to: /Users/mark/Library/Logs/CrashReporter/Adium.crash.log
Jul 9 12:01:06 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 12:01:07 mesenko crashdump[368]: Adium crashed
Jul 9 12:01:09 mesenko crashdump[368]: crash report written to: /Users/mark/Library/Logs/CrashReporter/Adium.crash.log
Jul 9 12:22:41 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 12:22:49 mesenko crashdump[391]: Adium crashed
Jul 9 12:23:02 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 12:23:03 mesenko crashdump[391]: crash report written to: /Users/mark/Library/Logs/CrashReporter/Adium.crash.log

Unfortunately the crash log doesn't exist.

Catfish_Man wrote:Also Adium shouldn't be capable of causing a system lockup, which makes it particularly interesting. Have you been filing crash reports when possible? (and, as jstamos notes, are you running 0.82?) If so, if you could tell me what email or IM name you filed them as I could have a look and see if I could find out what's causing them (besides the fact that file transfer doesn't work very well).

zaudragon · Post by **zaudragon** » Sun Jul 10, 2005 5:28 am

The_Tick wrote:How did that force a reboot? You couldn't just force kill adium?

I *could* since I did it multiple times. But once I try to switch apps… force reboot is needed.

Post by **The_Tick** » Sun Jul 10, 2005 5:34 am

zaudragon wrote:
The_Tick wrote:How did that force a reboot? You couldn't just force kill adium?
I *could* since I did it multiple times. But once I try to switch apps… force reboot is needed.

Again, once you force killed adium, how was a reboot required?

Post by **evands** » Sun Jul 10, 2005 6:19 am

mesenko wrote:Jul 9 09:46:14 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:46:41 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:47:01 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:47:22 mesenko kernel[0]: disk0s3: I/O error.
Jul 9 09:47:47 mesenko kernel[0]: disk0s3: I/O error.

You've got problems, and they ain't Adium related. Recommend booting from your OSX install DVD/CD, running Disk First Aid from the Utilities menu, and choosing Verify And Repair for your hard drive. If it finds errors it can't repair, see if your hard drive is still under warranty.

reversed · Post by **reversed** » Sun Jul 10, 2005 6:34 am

ooooh bummer mesenko. that's rough. the pinhole leak becomes a flood.

i feel you man.

zaudragon · Post by **zaudragon** » Sun Jul 10, 2005 3:55 pm

The_Tick wrote:
zaudragon wrote:
The_Tick wrote:How did that force a reboot? You couldn't just force kill adium?
I *could* since I did it multiple times. But once I try to switch apps… force reboot is needed.
Again, once you force killed adium, how was a reboot required?

OK so:
1. Adium crashes when I try to switch to a faulty message style.
2. I try to switch apps.
3. Force Restart.

OR

1. Adium crashes when I try to switch to a faulty message style.
2. I force quit Adium.
3. I go on my merry way with a perfectly stable Mac…

FredAkbar · Post by **FredAkbar** » Sun Jul 10, 2005 4:09 pm

When you say a force reboot was required, do you mean the whole system just locks up, like you can't move the mouse or anything (this has happened to me once or twice after quitting Virtual PC), or does it kernel panic, or what?

zaudragon · Post by **zaudragon** » Mon Jul 11, 2005 1:40 am

FredAkbar wrote:When you say a force reboot was required, do you mean the whole system just locks up, like you can't move the mouse or anything (this has happened to me once or twice after quitting Virtual PC), or does it kernel panic, or what?

Mouse moves, beachball, clock stops.

I think I need more RAM; that might be the problem… only 256MB of it.

cocoaforge

continuous crashing after yahoo file xfer

continuous crashing after yahoo file xfer

Re: continuous crashing after yahoo file xfer

yahoo file xfer crash info

Re: yahoo file xfer crash info