Armory crashing when I import my wallet

[Moscow999]

Hello. I am new to Armory. I have Armory version .93, and the Bitcoin core version v0.10.0. I am using them on a Windows 7 machine. When I start the program with no wallets imported, it appears to work with out issue. It successfully completes the steps of initializing the bitcoin engine, and will present the window which says that blockchain loading is complete. However when I import my wallet it starts to give me problems. It will rarely finish scanning my wallet before crashing. Also, if I try and restart Armory after I have imported my wallet, it will crash immediately upon program start. This is what the Windows event viewer says about the crash:

"Windows cannot access the file  for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program ArmoryQt.exe because of this error."

One strange thing that occurs when I first import my wallet to Armory, and the program says that it is scanning, is that Armory slowly starts to take up more and more of my RAM, up until it is utilizing up to 95% of the 16 Gigabytes I have on my system.

I have uninstalled and reinstalled completely, several times on two different drives, and I still get the same crashes. The only thing that ever remedies the situation is if I delete my wallet files from the directory "C:\Users\User\AppData\Roaming\Armory" folder. After that, Armory seems to work like a dream again, even without a reinstall. But of course it isn't much use without an imported wallet.

[1714920082]

1714920082

[1714920082]

1714920082

[1714920082]

1714920082

[goatpig]

Let's see some log files

[lopery]

Mine keeps crashing too!

log file:

[Moscow999]

I'm sorry for the delay: http://paste.ubuntu.com/10456315/

[goatpig]

Both of you will need the fix in https://bitcointalk.org/index.php?topic=970983.0

If you build the binaries on your own, just go ahead and pull the fix and try it out.

If you depend on the release builds, turn off bitcoind auto-management and run BitcoinQt manually, this will mitigate the issue. You will have to rebuild and rescan if you are going to use BitcoinQt as it won't fix the issue, just prevent it from reoccurring. The fix will repair bad DBs on its own though.

[Moscow999]

Is there any other setting that I need to change when I turn off bitcoinQT auto-management in Armory? When I manually start bitcoinQT and armory, I can not get armory to connect to the network at all. Nothing happens when I click the "Go Online" button. I have unchecked the "Let armory run bitcoinQT/bitcoind" option. Is there another option that I am missing, perhaps in some config file somewhere?

[goatpig]

Is there any other setting that I need to change when I turn off bitcoinQT auto-management in Armory? When I manually start bitcoinQT and armory, I can not get armory to connect to the network at all. Nothing happens when I click the "Go Online" button. I have unchecked the "Let armory run bitcoinQT/bitcoind" option. Is there another option that I am missing, perhaps in some config file somewhere?

1) Start BitcoinQt, let it sync

2.a) If you are using a custom folder for BitcoinQt's block data, you have to tell Armory where to look. Assume you are using C:\Bitcoin for your BitcoinQt folder (you are running BitcoinQt with the -datadir="C:\Bitcoin" argument), you need to run Armory with the --satoshi-datadir="C:\Bitcoin" argument.

2.b) Under certain conditions Armory fails to automatically resolve your Core blocks folder, even if it's in the default location. In this case you'll have to force that path with the --satoshi-datadir arg.

3) Start Armory, it should figure find the running BitcoinQt instance right away. Otherwise, log files.

[Moscow999]

Ok, that seemed to do the trick. Armory is connecting and building the databases now. However, Armory is still insisting on building the databases in the default folder "C:\Users\owner\appdata\roaming\Armory". I have changed the folder in the settings menu to no avail. Is there a similar argument that will change the default database folder?

[goatpig]

Ok, that seemed to do the trick. Armory is connecting and building the databases now. However, Armory is still insisting on building the databases in the default folder "C:\Users\owner\appdata\roaming\Armory". I have changed the folder in the settings menu to no avail. Is there a similar argument that will change the default database folder?

Can't set that in the setting menu. use --dbdir instead

[Moscow999]

Thank you for your help so far. Armory seems to be connecting to the network properly, and building databases in the appropriate directories. Unfortunately once I import my wallet, the behavior is the same. The program crashes immediately upon every start up with a wallet imported. Here is my most recent log file: http://paste.ubuntu.com/10511568/

[goatpig]

I need to see armoryccplog.txt

[Moscow999]

http://paste.ubuntu.com/10517986/

[goatpig]

Delete your log files and Armory's databases folder. Start Armory with your wallet loaded from the start and let it go all the way, then post your log files.

[Moscow999]

Ok, done. Here are the log files.

Armorycpplog: http://paste.ubuntu.com/10519072/
Armorylog: http://paste.ubuntu.com/10519099/

[goatpig]

Log says it's working currently

[Moscow999]

Is there any other avenue you can suggest for troubleshooting this? The behavior is the same: immediate crashes at startup after a wallet is created or imported in armory.

[goatpig]

For now try the new build with the fresh fixes, but your logs did not indicate anything that would lead me to believe these fixes will cover your issue. At any rate, try and it report here.

[Moscow999]

I did a fresh install of Windows 7 on my PC, and now Armory seems to be working perfectly.

[goatpig]

I did a fresh install of Windows 7 on my PC, and now Armory seems to be working perfectly.

Glad to hear