If a computer is infected, it is completely hopeless

Let say you generated an address with the cold system, which is "1User". You send a withdrawal request to the exchange, asking them to send bitcoin to 1User. A sophisticated malware could secretly replace the address with "1Hacker" before sending the request the exchange.

Generate the new addresses on your cold system first, and then verify that the addresses you generate on the hot watch-only system match the addresses in the cold system.

I'm eating lunch with altoz right now and he also says he's had problems with 0.90 that required him to delete the .armory directory.

I think you've got a lot of users who having problem but are just living with them instead of reporting them.

2. Not sending pooled funds into Armory.  I send them every once in a while when it's as much as feel comfortable leaving in a web wallet.

I'm not saying that no one has problems with Armory.  But we got 25,000 downloads each of the last two months, and we get only a handful of support requests each day.  Unfortunately, it's still too much, as we need to focus on developing and we're not a customer support house, but we're doing our best to balance everything.

In that particular thread that is linked, we have a problem with certain types of transactions that is affecting at least 2 of the 3 users there reporting issues (which are in this thread).  I suspect this pattern is present across a lot of support requests.   I whole-heartedly agree that we need to get the app working for those users, but they still represent a small portion of our userbase -- those that are participating in pooled mining.  In fact, my neighbor who knows nothing about Bitcoin was able to get Armory running and using it, though she said it took 58 hours to sync.

0.91 is an improvement over 0.90 for sure.  But we don't believe that it's a critical upgrade.

Sorry in advance for being blunt, but when it comes to releasing 0.91 you guys really need to shit or get off the pot.

Right now you don't have any viable downloads on your website. The 0.8x series is too resource-intensive for most users, and 0.90 is unusably crash-prone.

A year ago, I could point people in this situation: http://www.fr33aid.com/1511/fr33-aid-bitcoins-stolen/ at your website and know they'd find something there they could download and use, but that hasn't been true for the last six months and I don't see any particular acknowledgment of this or urgency on your part.

It's not a problem for me personally since I can just grab the 0.91 branch from Git, but a lot of people who can't are losing Bitcoins because there aren't any good usable cold storage solutions any more.

New features are great to have, but they shouldn't delay you having a minimal viable product out, where "minimum viable product" is defined as "an application that lets you send and receive bitcoins from cold storage without consuming obscene amounts of RAM and also doesn't crash every few seconds."

Do you mean this WO is ages old? I thought you had it exported from your recently restored wallets. If it is very old, now I really want to take a look at it.

Someome just recently sent us a WO that crashes Armory. I don't know if its yours but I'll be getting on it soon. I'm not gonna insist to see your WO until I'm done with the current one, however it may be very interesting. If anything don't delete it.

As for your test, you should try with a freshly derivated WO.

I've imported the WO wallet on 3 computers now with similar results.  On rig 2 I got the wallet imported and scanned but it would crash frequently (with 30 minutes) and now does load without crashing.  On rig 3 I've done a clean install of Ubuntu 12.04, updated and installed bitcoind and qt from the ppa, synced the blockchain and I'm having similar symptoms as rig 2 and 1 now.

I moved back to using 0.88.1 on rig 1 and it hasn't crashed after a few days. 

Would it make sense to try to reimport (from the paper fragments I have) and export the WO wallet and see if that works better or is that unlikely to do anything different?

Try that again with a watching only copy of your offline wallet. If that crashes too, send me a copy of your WO wallet and I can isolate the bug.

Okay I deleted everything in appdata/armory and added a new wallet "unused hack".  Let that sync.  Everything was peachy.  Stop and started Armory everything worked.
Added my offline wallet.  Crashed. Any Idea how I can fix this?  Or should I just hold tight?

6. Import wallet the I created using "watching only copy"
Armory Scans Transaction history.  Then crashes.