My armory breaks down every time I start it. Or better: as soon as it is connected to BitcoinQT (while organziing blockchain). I have the latest version of BitcoinQT and Armory. It was everything ok for weeks. But today it happend EVERY time (I tired at least 10 times, reboot, ...) I have a mac.
Any hint what I should do? Rebuilt blockchain? Reinstall Armory?
I use Armory on my Mac often and very rarely see crashes. I've heard some people are still having performance issues. My theory is that Qt (an underlying library) just doesn't play nice with some Macs due to threading issues. I've been trying to make some noise and get this investigated. If anybody would like to help me out,
please upvote this bug. The patch I posted there doesn't fix everything but it does fix a lot of issues. Maybe drawing more attention to it will lead to more long-term fixes.
*jumps off soapbox* Anyway, regarding this crash, if it happens again, look for the following bits of info.
Crashed Thread: 8
(...)
Thread 0:: Dispatch queue: com.apple.main-thread
0 libdispatch.dylib 0x00007fff8b59f7f8 _dispatch_queue_wakeup_with_qos_slow + 1075
1 com.apple.coreui 0x00007fff8d155bed PerformBlockWithThemeRegistry + 102
2 com.apple.coreui 0x00007fff8d155e7e _LookupThemeProvider + 232
3 com.apple.coreui 0x00007fff8d1391e1 -[CUIThemeFacet _approximateRenditionForRenditionKey:] + 109
4 com.apple.coreui 0x00007fff8d13e706 -[CUIThemeFacet imageSize] + 83
The crashed thread will test you which trace to post, which is the gobbledygook at the bottom of my quote. I'm guessing it'll be a Qt issue but I could be wrong.
Also, just curious, do you put your Mac to sleep often? I do get the odd crash on Yosemite after I've put my Mac to sleep something like 12-15 times, along with other odd behavior. Some of it might be Armory - I'm investigating right now - and some of it is almost certainly Qt (or Yosemite causing Qt to freak out).