[BOUNTY 0.03/bug] Help test next major release of Armory! (0.91.1)

[qnxt]

0.90.99.5 pegs one CPU core on OS X when anything besides the main window is open. This happens with Send Bitcoins, Receive Bitcoins, Wallet Properties, Offline Transactions, and even the About box.

It drops back down after 1 - 2 minutes of being idle in the background, but that appears to be due to App Nap. If I get info on the app and disable App Nap, then Armory eats CPU indefinitely. (Or if I leave it in the foreground.)

9553   Python       99.2 01:44:17 8/1  1    156-  2265   286M-  797M+  0B     17M    2021M  4556M  9549  9549  running  501

ps output over 5 minutes after clicking Receive Bitcoins, then letting it sit at "Select Wallet" in the background:

Wed Apr  2 20:41:01 EDT 2014
x         29597  99.0  6.0  3739228 503900   ??  R     8:34PM   5:16.55 /Applications/Armory.app/Contents/MacOS/Python /Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py

Wed Apr  2 20:46:02 EDT 2014
x         29597  60.7  6.0  3849040 507088   ??  R     8:34PM  10:07.81 /Applications/Armory.app/Contents/MacOS/Python /Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py

Armory is still pretty responsive for me even when it's doing that (much more than 0.90.99.4), and if I go back to the main window, CPU usage drops back down. (It only used about 2 or 3 seconds of CPU time over 5 minutes at the main window.) I have a total of 4 wallets with around 100 addresses and 200 transactions.

Edit: Still happening in 0.90.99.7.

[Natanael]

Another 99% crash.

http://imgur.com/XdpxWRy

Did you wipe your previous DB before building with 0.90.99.5?

Not yet, will try.

[goatpig]

I accidentally reverted the 99% fix in 0.90.99.5. Wait for .6 for the fix of the fix =P

[TheAwer]

Another thing: I had Armory open when Bitcoin Core was catching up, and Armory was updating the database (or whatever it does).  I got a notification that Armory was online and had finished loading, but when I checked Bitcoin Core there were still 13 hours to catch up on.  After I clicked the close button (or whatever the okay button is called), Armory froze.  It's still frozen now.

EDIT: It unfroze.  Also, in the bottom right, it says "Connected (0 blocks)", if that's any help.

EDIT EDIT: I restarted and it worked fine.

[goatpig]

Another thing: I had Armory open when Bitcoin Core was catching up, and Armory was updating the database (or whatever it does).  I got a notification that Armory was online and had finished loading, but when I checked Bitcoin Core there were still 13 hours to catch up on.  After I clicked the close button (or whatever the okay button is called), Armory froze.  It's still frozen now.

EDIT: It unfroze.  Also, in the bottom right, it says "Connected (0 blocks)", if that's any help.

EDIT EDIT: I restarted and it worked fine.

The current Armory model doesn't play so nice with a heavily back tracked Bitcoin Core. Ideally you want to either automanage bitcoind, in which case Armory will make sure bitcoind is fully sync'd before processing further, or let BitcoinQt sync before running Armory.

This may change in the future, as the model is getting overhauled.

[japandrew73]

Overall after testing with OSX 10.9.2 running offline transactions from my Pi, I'd say you guys did some pretty great work with this last release!

Great job

[Brangdon]

I'm pretty sure that goatpig already fixed this.

It is indeed fixed in 0.91-beta. (At least, it let me send to two addresses; I didn't try three.)

Do you want updates on what other bugs are or aren't fixed in this version?

[goatpig]

I'm pretty sure that goatpig already fixed this.

It is indeed fixed in 0.91-beta. (At least, it let me send to two addresses; I didn't try three.)

Do you want updates on what other bugs are or aren't fixed in this version?

sure, keep 'em coming

[jl2012]

In "Update Software", it fails to determine Windows Server 2012 R2, which should be equivalent to Windows 8

[veyp0r]

Hi,

Is source code available for this release? I found a few binaries/packages , but there doesn't seem to be anything on GitHub matching this release number.

Thanks!

[jl2012]

This is not a new bug but is not get fixed. I can import 0000000000000000000000000000000000000000000000000000000000000000 as private key (which is invalid), and the address will be shown as 16QaFeudRUt8NYy2yzjm3BMvG4xBbAsBFM. When I try to spend the bitcoin in that address, Armory crashed.

[qnxt]

So...you guys closing out the bounties since 0.91 is out?

[etotheipi]

So...you guys closing out the bounties since 0.91 is out?

Sorry for the delay... I totally got swamped and forgot about the bounties.  I will compile a list of first-reported bugs and then have people PM their addresses to me.

However, we're about to do a 0.91.1 release with some tweaks and notifications regarding corrupt wallet reports.  Unless I hear complaints... I would like to just merge it all into one bounty campaign and pay out all at once.  Since the changed in this point release are so minimal and isolated, it should be a very quick testing phase

[etotheipi]

(updated top post and copied here)


Find bugs in Armory 0.91.1, get 0.03 BTC!

This thread used to be for the 0.91 release, but I'm going to piggyback on it for for 0.91.1 because it's basically the same release, but with some minor tweaks.  Nothing substantial should've changed, except for the bug reporting and wallet-corruption handling.  This was born out of a couple reports of wallet corruption that were not being handled well by Armory in 0.91, and we had to not only improve it but add a way for users to submit their wallet recovery logs for review. 

Given that this will be pretty boring, I've upped the bounty to 0.03 BTC (~$15) per bug.  I will pay out all bounties for the original 0.91 testing and this round at the same time.  I expect this round won't be very long, and the same rules apply -- you must be the first to post it, and it must be something that isn't totally trivial.  But we're not going to be stingy about it -- we need testers more than we need to save $15 on this bounty!

This release might require explicit digging for bugs.  There might a few pieces of low-hanging fruit, but beyond that you're going to have explicitly test some of the less-commonly-used functionality (importing, sweeping, rebuilding, making & restoring backups, etc). 

https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.91.1-rc1_32bit.deb
https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.91.1-rc1_64bit.deb
https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.91.1-rc1_osx.tar.gz
https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.91.1-rc1_raspbian.tar.gz
https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.91.1-rc1_winAll.exe

Due to my build scripts breaking I wasn't able to go through the official release process for the testing build.  So I have signed the hashes with my regular GPG key (not the offline key).  While this is in testing, I'll be rewriting the build & release scripts and everything will be done properly by the time we actually release.

https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.91.1-rc1_sha256.txt.asc

[Corelianer]

Thank you for the great improvements especially the security allert system and the torrent downloader.

UI:
- A cosmetic uglyness: Windows 7 64Bit. When you open the settings the window upens so that you have also a vertical scroll-bar.


Secure Downloader:
- Armory could not find an appropriate download for your operating system. You have to manually select the correct download on the next window.

Debug Log:
- The debug log says "System is 64-bit      : False". But my system is indeed Windows 64-Bit. (Maybe because the ArmoryQt.exe is a 32-bit application?)

Torrent Download:
- How can I find out if the torrent download is working and at what speed? Is it only downloading or also seeding?

Wallet Creation Wizard:
- Creating a password with just 5 letters is possible and I'm not warned that my password would be very-weak.


Paper Backup:
- Frame is overlapping with the Root-Key in the preview as well as in the printout (FYI the printscreen is from a empty wallet, no bitcoins to steal )

[qnxt]

No problem; merging them makes sense.

I can't even open 0.91.1 on OS X 10.9.2 due to a library issue. Just closes immediately when I double-click, and if I launch it manually:

/Applications/Armory.app/Contents/MacOS$ ./Armory
Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py", line 34, in <module>
    from armoryengine.ALL import *
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/ALL.py", line 1, in <module>
    from armoryengine.ArmoryUtils import *
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/ArmoryUtils.py", line 39, in <module>
    from CppBlockUtils import KdfRomix, CryptoAES
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/CppBlockUtils.py", line 28, in <module>
    _CppBlockUtils = swig_import_helper()
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/CppBlockUtils.py", line 24, in swig_import_helper
    _mod = imp.load_module('_CppBlockUtils', fp, pathname, description)
ImportError: dlopen(/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/_CppBlockUtils.so, 2): Symbol not found: __ZTVN8CryptoPP18StringSinkTemplateISsEE
  Referenced from: /Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/_CppBlockUtils.so
  Expected in: flat namespace
 in /Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/_CppBlockUtils.so

[etotheipi]

About OSX: 

Looks like the package didn't get fully recompiled.  I just wiped the mac directory and then recompiled from scratch (which takes forever, btw).  let me know if this works better:

https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.91.1-rc2_osx.tar.gz


About Raspberry Pi:

I finally got my RPi up and was able to collect the dependency tree.  Bundled it up into a tar.gz.  You should be able to copy that to the RPi and "sudo dpkg -i *.deb" from the unpacked tar.gz directory.  After that, you should be able to simply unpack the tar.gz and run Armory.  Please try it:

https://s3.amazonaws.com/bitcoinarmory-testing/armory_raspbian_deps.tar.gz


@Corelianer:

Thanks for all the reports.  Admittedly, a couple things (like password length and complexity) is a design design decision, not a bug.  I'll look more closely at what you put there, and might consider a couple trivial things to be worth one bounty together.  I'll let you know soon, and you can appeal appropriately

If it is using torrent, it is very explicit:  the main window will show you "Synchronizing using Armory CDN" and it will tell you download speed and number of peers.  Uploading is disabled -- we are running about 30 seedboxes to make up for that.  Based on some conversations on the Bitcoin mailing list, this may be obsolete soon, as the core devs seemed to have figured out how to make P2P synchronization just as fast (though it'll probably be like 6 months before it actually gets into Bitcoin core).

[KaChingCoinDev]

Issue:

Downloader is 0.9.0 for Bitcoin. Bitcoin is on 0.9.1, 0.9.0 had bad OpenSSL. Screenshot:




I don't know if it qualifies as a bug, but here is my BTC addy:
1Pi7AD6hUw3SBbFR5bPxxiZ6cH5hBF4fSM

[etotheipi]

Issue:

Downloader is 0.9.0 for Bitcoin. Bitcoin is on 0.9.1, 0.9.0 had bad OpenSSL. Screenshot:

<img>


I don't know if it qualifies as a bug, but here is my BTC addy:
1Pi7AD6hUw3SBbFR5bPxxiZ6cH5hBF4fSM

I'll give it to you because technically you're right  Updating that download was going to be part of this release you're testing right now!  It's not critical because the way Armory runs bitcoind 0.9.0 does not expose the OpenSSL bug.  

[KaChingCoinDev]

Issue:

Downloader is 0.9.0 for Bitcoin. Bitcoin is on 0.9.1, 0.9.0 had bad OpenSSL. Screenshot:

<img>


I don't know if it qualifies as a bug, but here is my BTC addy:
1Pi7AD6hUw3SBbFR5bPxxiZ6cH5hBF4fSM

I'll give it to you because technically you're right  Updating that download was going to be part of this release you're testing right now!  It's not critical because the way Armory runs bitcoind 0.9.0 does not expose the OpenSSL bug.  

Thanks   Let me know when you send the coins