Armory 0.96.1 started crashing suddenly (a macOS-specific question)

[pf]

It was working fine the other day. Today, it's crashing on launch. I even tried clearing out the AppSupport data folder. It still crashes on launch. Any ideas?

Code:

Process:               Python [4302]
Path:                  /Applications/Armory.app/Contents/MacOS/Python
Identifier:            com.armory.armory
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Python [4482]
User ID:               ***

Date/Time:             2017-08-01 ***
OS Version:            Mac OS X 10.12.6 (16G29)
Report Version:        12
Anonymous UUID:        ***


Time Awake Since Boot: 25000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Illegal instruction: 4
Termination Reason:    Namespace SIGNAL, Code 0x4
Terminating Process:   exc handler [0]

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   _CppBlockUtils.so             	0x000000010ba6e3c2 void CryptoPP::GetUserKey<unsigned int>(CryptoPP::ByteOrder, unsigned int*, unsigned long, unsigned char const*, unsigned long) + 450
1   _CppBlockUtils.so             	0x000000010bae2045 CryptoPP::Rijndael::Base::UncheckedSetKey(unsigned char const*, unsigned int, CryptoPP::NameValuePairs const&) + 197
2   _CppBlockUtils.so             	0x000000010ba97204 CryptoPP::AutoSeededX917RNG<CryptoPP::Rijndael>::Reseed(unsigned char const*, unsigned long, unsigned char const*, unsigned char const*) + 196
3   _CppBlockUtils.so             	0x000000010ba97002 CryptoPP::AutoSeededX917RNG<CryptoPP::Rijndael>::Reseed(bool, unsigned char const*, unsigned long) + 450
4   _CppBlockUtils.so             	0x000000010b82aab0 SecureBinaryData::GenerateRandom(unsigned int, SecureBinaryData) + 80
5   _CppBlockUtils.so             	0x000000010b86b383 BlockDataManagerConfig::BlockDataManagerConfig() + 467
6   _CppBlockUtils.so             	0x000000010b9cdb04 _wrap_new_BlockDataManagerConfig(_object*, _object*) + 68
7   org.python.python             	0x00000001002ffbd0 PyEval_EvalFrameEx + 30112
8   org.python.python             	0x00000001002f82a4 PyEval_EvalCodeEx + 2100
9   org.python.python             	0x000000010028078b function_call + 363
10  org.python.python             	0x00000001002596f3 PyObject_Call + 99
11  org.python.python             	0x0000000100267848 instancemethod_call + 232
12  org.python.python             	0x00000001002596f3 PyObject_Call + 99
13  org.python.python             	0x00000001002b986f slot_tp_init + 175
14  org.python.python             	0x00000001002b5a2b type_call + 347
15  org.python.python             	0x00000001002596f3 PyObject_Call + 99
16  org.python.python             	0x00000001002ffd10 PyEval_EvalFrameEx + 30432
17  org.python.python             	0x00000001002f82a4 PyEval_EvalCodeEx + 2100
18  org.python.python             	0x00000001002f7a66 PyEval_EvalCode + 54
19  org.python.python             	0x0000000100318721 PyImport_ExecCodeModuleEx + 241
20  org.python.python             	0x000000010031b7eb load_source_module + 1051
21  org.python.python             	0x000000010031b26f import_submodule + 271
22  org.python.python             	0x000000010031acf8 load_next + 280
23  org.python.python             	0x0000000100319d0e PyImport_ImportModuleLevel + 1214

[goatpig]

need logs.

[pf]

need logs.

What logs? I don't see any logs in the AppSupport folder. I only see an empty database folder in there. (This is after launching Armory with an empty AppSupport folder.)

If you mean the logs in Console.app, here are those (I filtered for "Armory" in Console.app):

Code:

default	10:17:10.649254 +0200	Python	WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.6 instead of 10.12.6. This is not a bug in Gestalt -- it is a documented limitation. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
default	10:17:10.649446 +0200	Python	0   CarbonCore                          0x00007fff9fb9a1b1 ___Gestalt_SystemVersion_block_invoke + 121
default	10:17:10.649473 +0200	Python	1   libdispatch.dylib                   0x0000000100be78fc _dispatch_client_callout + 8
default	10:17:10.649497 +0200	Python	2   libdispatch.dylib                   0x0000000100be78b9 dispatch_once_f + 38
default	10:17:10.649519 +0200	Python	3   CarbonCore                          0x00007fff9fb28292 _Gestalt_SystemVersion + 976
default	10:17:10.649540 +0200	Python	4   CarbonCore                          0x00007fff9fb27aad Gestalt + 139
default	10:17:10.649561 +0200	Python	5   QtCore                              0x00000001041106bc _ZN16QSettingsPrivate6createEN9QSettings6FormatENS0_5ScopeERK7QStringS5_ + 76
default	10:17:10.649582 +0200	Python	6   QtCore                              0x00000001040f2032 _ZN9QSettingsC1ERK7QStringS2_P7QObject + 34
default	10:17:10.653678 +0200	Python	MacOS error: -67062

Does this help?

[goatpig]

I mean armorylog.txt and dblog.txt, found in your Armory datadir.

[pf]

I mean armorylog.txt and dblog.txt, found in your Armory datadir.

There were no such logs in the folder. Looks like it was crashing before those logs got created.

Anyway. Recompiling Armory fixed the problem. I compiled it exactly as before: master branch + libpng version fix, compiled on a clean virtual machine.  The .app then dragged from virtual machine to normal macOS.

I wonder why the crashes started happening.

This is the only thing that changed between the no-crash and crash: I moved from a MacBook Pro laptop to an iMac. Exactly the same OS, booted from an external drive. The Armory.app was exactly the same.

This begs the question: Does Armory.app, when launched, change anything within Armory.app itself that could make it device-dependent?

This is probably a good question to ask Mr. Roark.

[droark]

This begs the question: Does Armory.app, when launched, change anything within Armory.app itself that could make it device-dependent?

I'm not aware of anything but Apple can and has done a lot of weird stuff in the past. Getting straight answers for these kinds of questions isn't easy.

[conchita]

Guys,

I'll try to be as brief as I can, and thank you for your assistance in advance.

Facts:

MacOS Sierra 10.12.6.
Installed Armory 0.96.1 for Mac OS.

Problem:

Cannot open Armory.

Attempts:

Allowed the app though System Preference - nothing.
Installed previous versions - nothing.

I have no coding background, and would appreciate your expertise on this matter.

Many thanks,

C

[HCP]

As above, you will need to post the armorylog.txt and dblog.txt, found in your Armory datadir.

Please use pastebin.com and then post the pastebin.com links here

[conchita]

HCP,

Thank you for your prompt response.

How do I get to armorylog.txt and dblog.txt?

Thanks in advance,

C

[conchita]

Can anyone assist me with the above?

A

[Roy Badami]

I've been seeing the same since updateing my Mac from 10.11.4 to 10.12.4.

I'm guessing it's an issue with some recent update to OS X.

[droark]

HCP,

Thank you for your prompt response.

How do I get to armorylog.txt and dblog.txt?

Thanks in advance,

C

Read this first. If Armory still doesn't run, go to /Library/Application Support/Armory and get the log files from there.

I'll be out of town for a couple of weeks, by the way. Won't be able to answer questions. Best wishes!