@ Gladamas

FYI, my Win7-64bit VM with 2GB of RAM and Bitcoin-Qt 0.6.3 has had Armory open for 2 days and has not crashed yet.  So, unless there is a specific trigger someone can point me to, I'm going to have to let this bug through for now.  Please let me know more details about the crashing, and hopefully I'll find a way to replicate it in the future.

However, I'm very close to a 0.82.1 version with full logging.  This will improve the situation a lot, since every crash can now be accompanied by a full log file of every informational message and error message, without the user even doing anything.   I will hopefully have that out tonight, and those of you experiencing crashes will only have to send me your armorylog.txt file after the crash.

@ kuzetsa

Are you waiting for address migration to try out Armory at all?  I highly recommend, even if migration was working, that you still create new addresses and send coins to them instead of importing just a couple addresses.  When you "migrate" addresses to Armory, you should really stop using those addresses in bitcoin-qt.  It really needs to be all-or-nothing.  This will avoid lots of issues with maintaining the same address in multiple programs (coins can get locked, and balances will be incorrect in both programs).  This is not an Armory limitation, it's an issue with Bitcoin-Qt which assumes no other program is using the same addresses.

Until then, you should create a new Armory wallet, send some coins to it, and if you want to go back, just send the coins back to your Bitcoin-Qt wallet.