Adium

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#11508 closed crash (fixed)

MSN crash after Retrieving Buddy List 100%

Reported by: J Owned by: nobody
Milestone: Adium 1.4 Component: Service/MSN
Version: 1.3.2 Severity: normal
Keywords: mergeto1.3.x Cc:
Patch Status:

Description

One of my three MSN accounts is causing Adium to crash upon "Retrieving Buddy List 100%". This was with 1.3.2. I installed 1.3.3b1, just to see if the problem had been fixed, but it, unfortunately, crashes as well. The MSN account has two contacts, and is accessible via Microsoft Messenger. Attaching crash logs from both.

Attachments (2)

Adium_2008-12-27-225526_JustenBook.crash (34.6 KB) - added by J 11 years ago.
Crash log from 1.3.2.
Adium_2008-12-27-234538_JustenBook.crash (33.9 KB) - added by J 11 years ago.
Crash log from 1.3.3b1.

Download all attachments as: .zip

Change History (11)

Changed 11 years ago by J

Crash log from 1.3.2.

Changed 11 years ago by J

Crash log from 1.3.3b1.

comment:1 Changed 11 years ago by zacw

Label me honestly perplexed. The only time we're using strcmp/strncmp in -updateFriendlyNameAfterConnect we're checking for a NULL pointer before doing so. The only time we're not is when we're checking against the UID or formattedUID, both of which should be set.

Do you have a friendly name set (in the Personal tab for the account)? What is it? Can you try setting one?

What is your UID (username/email/whatever) set to?

comment:2 Changed 11 years ago by J

I did, indeed, have a Display Name set under the Personal tab, and it was not unique. Upon removing that, and leaving that field blank, I can now connect without a crash...

comment:3 Changed 11 years ago by J

The friendly name was simply set to my first and last name, with a space in between (and no nonstandard characters for what it's worth). The username was first.last@….

comment:4 Changed 11 years ago by Dimmuxx

  • Milestone set to Adium 1.3.x

comment:5 Changed 11 years ago by zacw

(In [26177]) My best-guess as to why #11508 occurs is that we're accessing the PurpleAccount badly. Refs #11508.

comment:6 Changed 11 years ago by zacw

  • Milestone changed from Adium 1.3.x to Adium 1.4

comment:7 Changed 11 years ago by jas8522

J: If you can still reproduce this crash by re-entering your name in the account preferences with 1.3.3, try using a 1.4 nightly and see if you can still reproduce it. Then we'll know if Zac's guess was right or not

comment:8 Changed 11 years ago by zacw

  • Resolution set to fixed
  • Status changed from new to closed

Considering this fixed until shown otherwise.

comment:9 Changed 11 years ago by Robby

  • Keywords mergeto1.3.x added
Note: See TracTickets for help on using tickets.