cocoaforge

In the past day Adium has started freezing up whenever I start up the program. I can get to my contacts to load but then it freezes. I haven't seen anything about this so far posted in the forums. I've tried uninstalling and then re-installing version .86 and even gone as far as trying the newest beta version but it keeps freezing. Currently I have Adium .86 installed and I don't have ANY accounts set up and it's still freezing up (not crashing mind you) even with no accounts set up. My operating system is 10.2.8 if that makes any difference. I'm really in a rut and I was wondering if anyone has had this problem and if there's any fix to it. Thanks a ton!


Edit: I've also switched user accounts on my Mac and there's no luck with that either.

EDIT 2: HURRAY! It works again! I have no idea how it fixed itself. I was just running AOL AIM version 4.7 (curses) and it quit like it does a lot so I decided to try Adium again, for the hundredth time, and it just started working again. Weirdest thing ever. Made me realize how much I depend on Adium.

Have you tried deleting all the AdiumX files (including the preferences files) when you re-installed AdiumX? This freezing problem might be because of a preference file being corrupt or you can try restarting your computer which might fix the problem. On a side note, I'd recommend you to upgrade your OS .

-Zorg:-.

Zorg wrote:Have you tried deleting all the AdiumX files (including the preferences files) when you re-installed AdiumX? This freezing problem might be because of a preference file being corrupt or you can try restarting your computer which might fix the problem. On a side note, I'd recommend you to upgrade your OS .

-Zorg:-.

Yea, I did delete all Adium related files including the prefrences. I'll definatly look into getting 10.3 or 10.4 seeing how most applications seem to be requiring that these days. It just was just so sudden, it doesn't make any sense at all.

Edit: I have restarted the computer several times.

skipper9090 wrote: Yea, I did delete all Adium related files including the prefrences. I'll definatly look into getting 10.3 or 10.4 seeing how most applications seem to be requiring that these days. It just was just so sudden, it doesn't make any sense at all.

Try re-starting your computer and see if the problem still occurs. Also it could occur due to an external plugin or any xtras if you have anything like that installed.

-Zorg:-.

Edit: Also, check Console.app (located in /Applications/Utilities) See if there are any console messages when you open up Adium. Even though it's not crashing, just freezing, Console.app might show something related to Adium if it is missing anything or not.

Another Edit:

Edit: I have restarted the computer several times.

Oops.. I didn't see that, well then see if Console.app gives you any messages.

There's something more nefarious afoot as he's attempted this under another user (thus it would be relatively clean, if not totally clean) and restarted. Console output would certainly help, provided there is some.

bgannin wrote:There's something more nefarious afoot as he's attempted this under another user (thus it would be relatively clean, if not totally clean) and restarted. Console output would certainly help, provided there is some.

Sorry for my ignorance but how would I come about getting the console output? And I haven't installed any extenions or add-ons in the past 2 months or so.

Applications -> Utilities -> Console.app

use the search field to narrow down to Adium

Wow! It actually read something! That's amazing, I would have never thunk...

Dec 10 20:17:09 localhost crashdump: Crash report written to: /Users/denniswentland/Library/Logs/CrashReporter/atos.crash.log

2005-12-10 20:17:10.454 Adium[526] Caught exception: NSPortTimeoutException - [NSPortCoder sendBeforeTime:sendReplyPort:] timed out
2005-12-10 20:17:10.455 Adium[526] The following unhandled exception was ignored: NSPortTimeoutException ([NSPortCoder sendBeforeTime:sendReplyPort:] timed out)
Stack trace:
2005-12-10 20:17:10.456 Adium[526] [NSPortCoder sendBeforeTime:sendReplyPort:] timed out

Well, given that output it makes sense the behavior you are seeing (basically, some part of the communication has an error and since nobody gracefully took care of it the whole thing goes kaput)

As to why this occurred - I leave that to those who play in the bowels of the communications code [though I make take a stroll to see where this is used and if the problem is evident enough for me to fix, if possible]

*back to podcast recording*

bgannin wrote:Well, given that output it makes sense the behavior you are seeing (basically, some part of the communication has an error and since nobody gracefully took care of it the whole thing goes kaput)

As to why this occurred - I leave that to those who play in the bowels of the communications code [though I make take a stroll to see where this is used and if the problem is evident enough for me to fix, if possible]

*back to podcast recording*

Well thank you and everyone else, your efforts are greatly appreciated, if only I could fix this