cocoaforge

I'm a new convert. I've been using FIRE for a LOOONG time now. I launched Adium, and was happy that it found that I had been using FIRE, and tried to import my settings. Unfortunately, it crashed during the setup process, and doesn't seem to have completed the chat log transcript import section of set up. Is there anyway to rerun this manually? Or some other utility that I can run to do this?

I did search these forums and found reference to something in the developer section, but that info's circs 2004, and no longer seems to apply.

Any help would appreciated. I'd hate to have to switch back to FIRE because of this.

If you go to Preferences->Accounts and remove all the accounts, the setup assistant will run again next time you launch Adium. There's no other way to get to it at present, though in the future there will probably be a direct way to get to the importer.

If it crashes again, please post back here and I'll get you a build with some extra debug logging so we can hunt down (and hopefully fix) the problem.

I tried what you said on my work machine. And submitted I think 4 crash reports.

I did manage to get a partial import of my FIRE logs on one of my tries. On the others, it crashed and I relaunched. The logs are submitted from my forum name, so it's not hard hard to find.

Also, importing account from FIRe is still broken in regards to AIM accounts. I noticed that was "fixed" in 1.01, but the AIM account still needs to be deleted and readded.

Any thoughts?

I'm unable to compile Adium until a week from Thursday, so I can't make a debug build. If another developer could add NSLog logging to the Fire log importing method to see each file name as it's about to be imported, the Console would then tell us which log is crashing... and Graham could take a look at it.

If this isn't resolved when I'm available again, I'll take care of it.

I'll whip up a debug build this afternoon and post a link.

A debug build of Adium 1.0.1, with logging ... logging is ready now.

http://www.infinitenexus.com/AIFire101.zip

Ok, downloading...

Where are the logs stored? Who do i email them to? Post them here to the forum?

Or are we all fancy-like and Adium will auto-send them with the crash report?

Now that I look at the logs in Console, I don't want to post it to the forum, as there's other people's personal information in there. I don't think I need to post the contents of my buddlylist to a public forum.

Where/how would you like them?

They will write out to the console log, which you can access using Console (in Applications/Utilities) and you can then PM the relevant text to a developer [say, me] (it will start with base path: and then have a lot of entries for log path: full path: ) or post it here, depending on your privacy concerns.

Sent.

It's a memory issue:

Adium(492,0x38b4a00) malloc: *** vm_allocate(size=4121845760) failed (error code=3)
Adium(492,0x38b4a00) malloc: *** error: can't allocate region
Adium(492,0x38b4a00) malloc: *** set a breakpoint in szone_error to debug
Adium(492,0x38b4a00) malloc: *** error for object 0xa51afa8: Non-aligned pointer being freed
Adium(492,0x38b4a00) malloc: *** set a breakpoint in szone_error to debug

I'll forward the relevant information along to the developer who worked on this.

oh wow, nearly 4G of data. That is a lot to allocate. No wonder why it failed.

Yes, it is. Oddly enough, the folder that the FIRE conversations are kept is only about 23 MB. At least according to the Finder. And digging through some of the individual directories of people I talk to, that's about right.

Why it's requesting a 150x increase in memory is beyond me.

SIde note, both machines that are exhibiting the issue has 2GB+ of pfysical RAM. Not that that helps any.

Invalid pointer passed to malloc() or a friend, probably, not an actual legit desire to allocate that much memory.

IIRC each 32-bit process (i.e., anything ran on a machine that's not a G5 or Mac Pro) can only address 2GB of memory, so that's a bit of an issue.

That explosion certainly is odd.

I've sent the most recent crash log from my home machine.

just fyi:

Work: Dual 1.42 G4 2 or 3 GB RAM. Don't recall exact specs.

Home: MacBook CoreDuo 2.0 GHz 2GB RAM

Random cross-reference: #6378 is a completely different crash which logs something similar and is why I mention this.