Adium

Ticket #357 (closed defect: fixed)

Opened 5 years ago

Last modified 11 months ago

Adium 8.2 (b1 and b2) crash on launch

Reported by: twopeak <twopeak@gmail.com> Owned by: anybody
Milestone: Component: Adium Core
Version: 0.82 Severity: normal
Keywords: startup launch unhandled NSPortCoder exception crash growl registration registering register Cc: twopeak@…
Patch Status:

Description

Okay, filed a ticket, since it's easyer with attachements... I updated to beta two to be sure it wasn't something else, and I get the same problems as in beta one.

So the problem is that adium starts up, shows offline yahoo & icq contacts, and then I get the spinning beachball.

I cleared the console before launching and I get this:

2005-05-29 07:54:21.290 GrowlHelperApp[1532] Exception while forwarding notification: [NSPortCoder sendBeforeTime:sendReplyPort:] timed out

In attachement, I add the adium sample and the growl sample. If it's of any importance, I updated manually to growl .7 before adium started to use it. I use a G3 with not a lot of memory (128 I think) and MacOs X.3.9

Attachments

Sample of Adium.txt (5.5 KB) - added by twopeak <twopeak@…> 5 years ago.
Sample of Adium .8.2 beta (downloaded 10 minutes ago)
Sample of GrowlHelperApp.txt (2.6 KB) - added by twopeak <twopeak@…> 5 years ago.
Sample of Growl Helper app for Growl .7

Change History

Changed 5 years ago by twopeak <twopeak@…>

Sample of Adium .8.2 beta (downloaded 10 minutes ago)

Changed 5 years ago by twopeak <twopeak@…>

Sample of Growl Helper app for Growl .7

Changed 5 years ago by twopeak <twopeak@…>

am I going crazy? I keep on reading beta 2 and when I search again for it it neer says beta 2... pfffffff, so anyway, if I read wrong, ignore it... it's 8 in the morning and exams tomorrow.

Changed 5 years ago by boredzo

this is really a Growl bug. one of your forwarding destinations is down, and GHA (not having a timeout) is waiting indefinitely.

I've filed  Growl ticket 264, which calls for a timeout setting and controls to feed it. I'll close this ticket when that ticket is closed.

Changed 5 years ago by boredzo

hm. note to self: read description fully before commenting.

okay, so besides the timeout setting, we need exception handlers. I've filed another Growl ticket,  Growl ticket 265 for this.

Changed 5 years ago by boredzo

  • keywords startup launch unhandled NSPortCoder exception crash registration registering register added; startup, crash, removed

Changed 5 years ago by boredzo

  • cc twopeak@… added

Changed 5 years ago by boredzo

BTW, how long did you wait? I'm thinking that Growl is going through all of the forwarding destinations you have set, and none of them are reachable, so it looks like Growl is crashed when in fact it's simply taking a long time. Adium isn't crashed (as such) either; it's waiting on Growl.

Changed 5 years ago by twopeak <twopeak@…>

I waited about 3/5 minutes once. In general in Activity monitor I see that the names get red after 5/10 seconds of "beachballing" and get "(hung)" written behind them.

I'll try again to start adium and I'll come back in one hour or so when I stop studying, to be 100% sure!

Changed 5 years ago by twopeak <twopeak@…>

so, check the time, still beachballing...

Changed 5 years ago by evands

I believe this is resolved for Growl 0.7.1 in [ Growl revision 2604]

Changed 5 years ago by catfish_man

  • status changed from new to closed
  • resolution set to fixed

Calling this fixed based on evands' comment.

Changed 11 months ago by zacw

  • component changed from Core Adium to Adium Core
Note: See TracTickets for help on using tickets.