AOL unexpectedly quits

evildan

evildan

Super Moderator
A friend of mine has been using AOL (on OSX 10.2.2) for awhile now. Last week the application just started quitting.

It seems to be a timed thing. Launch of application starts normally, signing on occurs with no errors (TCP connection also checked another ISP source) but after about 2 minutes of connection time, the application unexpectedly quits. (Default error message: "AOL has unexpectedly quit, non of the other applications were effected.")

I've checked log files, and the crash generates an error report (pasted below). Does anyone have a clue what's happening here?

The counsel application reads: Jan 27 14:27:19 Friends-Computer crashdump: Crash report written to: /Users/friend/Library/Logs/CrashReporter/AOL.crash.log

That log reads:

-----begin error log-----
**********

Date/Time: _2003-01-27 13:13:20 -0600
OS Version: 10.2.2 (Build 6F21)
Host: _ _ _ friends-computer.local.

Command: _ _AOL
PID: _ _ _ _717

Exception: _EXC_BAD_INSTRUCTION (0x0002)
Code[0]: _ _0x00000002Code[1]: _ _0xa02212a0

Thread 0:
#0 _ 0x90074208 in mach_msg_trap
#1 _ 0x90006550 in mach_msg
#2 _ 0x9022a83c in SwitchContexts
#3 _ 0x902250e8 in YieldToThread
#4 _ 0x003c5dac in 0x3c5dac
#5 _ 0x001d37e0 in 0x1d37e0
#6 _ 0x001d2ddc in 0x1d2ddc
#7 _ 0x0019e3f4 in 0x19e3f4

Thread 1:
#0 _ 0x90074208 in mach_msg_trap
#1 _ 0x90006550 in mach_msg
#2 _ 0x902b0d90 in TS_exception_listener_thread
#3 _ 0x90021308 in _pthread_body

Thread 2:
#0 _ 0x90074208 in mach_msg_trap
#1 _ 0x90006550 in mach_msg
#2 _ 0x9022a83c in SwitchContexts
#3 _ 0x902250e8 in YieldToThread
#4 _ 0x902433e0 in SetThreadState
#5 _ 0x9026daec in SetThreadStateEndCritical
#6 _ 0x003c6de8 in 0x3c6de8
#7 _ 0x003c5284 in 0x3c5284
#8 _ 0x003c5180 in 0x3c5180
#9 _ 0x003c59ec in 0x3c59ec
#10 _0x003c71b4 in 0x3c71b4
#11 _0x9023be94 in CooperativeThread
#12 _0x90021308 in _pthread_body

Thread 3:
#0 _ 0x90074208 in mach_msg_trap
#1 _ 0x90006550 in mach_msg
#2 _ 0x9022a83c in SwitchContexts
#3 _ 0x902250e8 in YieldToThread
#4 _ 0x003c5dac in 0x3c5dac
#5 _ 0x001e1464 in 0x1e1464
#6 _ 0x012e6330 in 0x12e6330
#7 _ 0x003c71b4 in 0x3c71b4
#8 _ 0x9023be94 in CooperativeThread
#9 _ 0x90021308 in _pthread_body

Thread 4:
#0 _ 0x9000570c in syscall
#1 _ 0x90515d9c in BSD_waitevent
#2 _ 0x9051576c in CarbonSelectThreadFunc
#3 _ 0x90021308 in _pthread_body

Thread 5:
#0 _ 0x9003f068 in semaphore_wait_signal_trap
#1 _ 0x9003ee84 in _pthread_cond_wait
#2 _ 0x9051dda0 in CarbonOperationThreadFunc
#3 _ 0x90021308 in _pthread_body

Thread 6:
#0 _ 0x90042c48 in semaphore_timedwait_signal_trap
#1 _ 0x9003ee74 in _pthread_cond_wait
#2 _ 0x90233438 in TSWaitOnSemaphoreCommon
#3 _ 0x9023c258 in TimerThread
#4 _ 0x90021308 in _pthread_body

Thread 7:
#0 _ 0x9003f068 in semaphore_wait_signal_trap
#1 _ 0x9003ee84 in _pthread_cond_wait
#2 _ 0x9023341c in TSWaitOnSemaphoreCommon
#3 _ 0x90248aec in _Z15AsyncFileThreadPv
#4 _ 0x90021308 in _pthread_body

Thread 8 Crashed:
#0 _ 0xa02212a0 in _XHNDL_trapback_instruction
#1 _ 0xa02212a0 in _XHNDL_trapback_instruction
#2 _ 0x012b6040 in 0x12b6040
#3 _ 0x012b57ec in 0x12b57ec
#4 _ 0xa02212a0 in _XHNDL_trapback_instruction
#5 _ 0x011502b0 in 0x11502b0
#6 _ 0x01141964 in 0x1141964
#7 _ 0x0113f270 in 0x113f270
#8 _ 0x011412b0 in 0x11412b0
#9 _ 0x011464d4 in 0x11464d4
#10 _0x0110dddc in 0x110dddc
#11 _0x010fc41c in 0x10fc41c
#12 _0x01e865e4 in 0x1e865e4
#13 _0x01e853a8 in 0x1e853a8
#14 _0x0118a088 in 0x118a088
#15 _0x01189cb0 in 0x1189cb0
#16 _0x011a7b1c in 0x11a7b1c
#17 _0x011a782c in 0x11a782c
#18 _0x011a9ac0 in 0x11a9ac0
#19 _0x0025f5ec in 0x25f5ec
#20 _0x0025f4f4 in 0x25f4f4
#21 _0x0025d43c in 0x25d43c
#22 _0x0025ac68 in 0x25ac68
#23 _0x012e6330 in 0x12e6330
#24 _0x003c71b4 in 0x3c71b4
#25 _0x9023be94 in CooperativeThread
#26 _0x90021308 in _pthread_body

Thread 9:
#0 _ 0x9003f068 in semaphore_wait_signal_trap
#1 _ 0x9003ee84 in _pthread_cond_wait
#2 _ 0x90525b90 in CarbonInetOperThreadFunc
#3 _ 0x90021308 in _pthread_body

Thread 10:
#0 _ 0x90074208 in mach_msg_trap
#1 _ 0x90006550 in mach_msg
#2 _ 0x9022a83c in SwitchContexts
#3 _ 0x902250e8 in YieldToThread
#4 _ 0x003c5dac in 0x3c5dac
#5 _ 0x0025ac98 in 0x25ac98
#6 _ 0x012e6330 in 0x12e6330
#7 _ 0x003c71b4 in 0x3c71b4
#8 _ 0x9023be94 in CooperativeThread
#9 _ 0x90021308 in _pthread_body

Thread 11:
#0 _ 0x90074208 in mach_msg_trap
#1 _ 0x90006550 in mach_msg
#2 _ 0x901490a8 in CFRunLoopRun
#3 _ 0x9018157c in CFRunLoopRunSpecific
#4 _ 0x905e2d90 in _ZN21XIOAudioDeviceManager18NotificationThreadEPS_
#5 _ 0x905e2cac in _ZN9CAPThread5EntryEPS_
#6 _ 0x90021308 in _pthread_body

PPC Thread State:
_srr0: 0xa02212a0 srr1: 0x0008d030 _ _ _ _ _ _ _ _vrsave: 0x00000000
_ xer: 0x20000000 _ lr: 0xa02212a0 _ctr: 0x012b54b0 _ mq: 0x00000000
_ _r0: 0xa02212a0 _ r1: 0xf04063f8 _ r2: 0x016d4000 _ r3: 0xffffffff
_ _r4: 0x016d72a8 _ r5: 0x016d73a8 _ r6: 0xf0406430 _ r7: 0x626f6c20
_ _r8: 0x6e6f7420 _ r9: 0x61766169 _r10: 0xf04069af _r11: 0xa0221734
_ r12: 0x016d43cc _r13: 0x016c46a4 _r14: 0x00000000 _r15: 0x00000000
_ r16: 0x00000003 _r17: 0x016c3700 _r18: 0x016c46a4 _r19: 0x00000004
_ r20: 0x038726f0 _r21: 0xf0407548 _r22: 0x00000000 _r23: 0x00000000
_ r24: 0xffffffff _r25: 0x038726f0 _r26: 0x00000000 _r27: 0x00000004
_ r28: 0x00000000 _r29: 0x00000000 _r30: 0x0042c000 _r31: 0xf0407f00

---end error log----
 
Okay this problem is still occurring. I find this to be a crazy distraction.

My friend has been nice enough to leave the computer for me to work on it. But I feel this is all in vein, as I am no closer to solving the problem then two days ago.

I've contacted AOL, they say, this is "not a known issue."

I've installed Virex, it picked up and cleaned two viruses, but the problem persists.

Any thoughts?
 
dan, i'm assuming you've tried something as simple as trashing the pref file? aside from that, the best way i know to fix this is to get a real isp. aol isn't losing all that money for nothing.
 
yeah, this isn't my computer, so not my ISP either. I've presented this as an option to my friend, but they are not ready to make the move.

I have trashed all of the associated AOL files and re-installed the entire application. I've also tried to use AOL's uninstall, which, by the way, does NOT remove all the AOL files.

I realize AOL sucks, but for now, I'm still attempting to solve this problem, since it appears he is the only one in the world having it. :)
 
and why doesn't he upgrade to 10.2.3? safari is known to have problems with 10.2.2, maybe aol shares similar issues with it.
 
I'm sorry, I should have mentioned, I tried upgrading already.

His current OS: 10.2.3
AOL version: 10.2.1

I've been checking VersionTracker daily for an AOL upgrade, I heard one is due out any day.
 
No problem ed, I appreciate the attempt. This really is a mind boggling little error. I really wish I could find the source of it.

I think I'll spend the weekend on this problem. At this point, scrubbing the drive seems like admitting defeat. :)
 
It’s been a while since this thread was used, but i am now experiencing the EXACT same behavior. I am running the latest version of AOL under 10.2.8. Does anyone have any ideas how to fix this other than a fresh install of the entire system?
 
I had exactly the same problem a couple of months ago!

I was using 10.2.4 and AOL would manage to connect but then instantly cause an error.

I found that I could not update any software on my system without causing this. But the cause of this for me was actually my audiodriver (I use a digidesign MBox). I had to uninstall my driver whenever I wanted to go online.

Then one day...miraculously...it stopped! I dont know what happened, but I'm just glad it did! I wish I could tell you how, but at least maybe look into the audio drivers?
 
Well I did finally fix the problem. It was an annoying one to track down. AOL litters your system with a whole bunch of files. Most of these are database files and cache stores. When you reinstall AOL, it does not replace these files, but instead uses the old ones. This is why a reinstall was not helping. By installing AOL on a brand new system and one by one copying the old files to the new system I was able to track down the one file that was the problem.

The file ‘/users/shared/AOL/Access Numbers’ was the culprit. Here is my guess why. After AOL connects, it queries a central database of access numbers, and stores any changes of numbers to the ‘Access Numbers’ file. In my case, this file had become corrupt. So anytime the application tried to write to it, the application crashed. I threw the ‘Access Numbers’ file in the trash and restarted AOL. When AOL did its query, it created a new ‘Access Numbers’ file and went on its marry way. This new file was not corrupt like the old one, and therefore did not cause a problem.

Hope that my suffering may help someone in the future.

Oh, and for the record…. AOL SUCKS
 
evildan said:
Okay this problem is still occurring. I find this to be a crazy distraction.

My friend has been nice enough to leave the computer for me to work on it. But I feel this is all in vein, as I am no closer to solving the problem then two days ago.

I've contacted AOL, they say, this is "not a known issue."

I've installed Virex, it picked up and cleaned two viruses, but the problem persists.

Any thoughts?
Click to expand...

Just a workaround... I still have my AOL account and mine won't launch because of a problem in my other post about Shared Library errors. You mention logging on through a TCP connection. I can only assume that you are NOT dialing up via a modem. For now, I just load a browser and log in at aol.com. It's pretty simple.

HTH

Alex
 
Thank you, thank you thank you, teamteama..........

I had been having the same problem on my powerbook G4, and it was driving me crazy.......your solution worked perfectly! I also posted a copy of your solution at the Mac discussion forum on using OSX, since others have been having that problem as well. You are a genius!!!

JP


teamteama said:
Well I did finally fix the problem. It was an annoying one to track down. AOL litters your system with a whole bunch of files. Most of these are database files and cache stores. When you reinstall AOL, it does not replace these files, but instead uses the old ones. This is why a reinstall was not helping. By installing AOL on a brand new system and one by one copying the old files to the new system I was able to track down the one file that was the problem.

The file ‘/users/shared/AOL/Access Numbers’ was the culprit. Here is my guess why. After AOL connects, it queries a central database of access numbers, and stores any changes of numbers to the ‘Access Numbers’ file. In my case, this file had become corrupt. So anytime the application tried to write to it, the application crashed. I threw the ‘Access Numbers’ file in the trash and restarted AOL. When AOL did its query, it created a new ‘Access Numbers’ file and went on its marry way. This new file was not corrupt like the old one, and therefore did not cause a problem.

Hope that my suffering may help someone in the future.

Oh, and for the record…. AOL SUCKS
Click to expand...
 
Wow. Thanks. I'm sure this will come in handy one day, when I'm trying to troubleshoot this damn-ned app on my mom's iBook. :)
 
the thing about aol is there one of the only dial up isp's that dont disconnect you after 2 hours. for example last week i was on an average of 8 hours every night and was not cut off at any stage. i'm not saying aol is perfect but if broadband is not available in your area then an isp that dont disconnect you every two hours makes downloading them big files more fun. and don't tell me to use a download manager, because they cost money( unless you steal it).
 
You must log in or register to reply here.
Back
Top