Mac crashes though.
It would really help if you could provide a strack trace from the crash reporter:
On the OSX Terminal:
defaults write com.apple.CrashReporter DialogType Developer
BM - let me know if this is what you're looking for
Process: BitSharesX [48656]
Path: /Applications/BitSharesX 0.4.9.app/Contents/MacOS/BitSharesX
Identifier: org.bitshares.btsx
Version: .. (..)
Code Type: X86-64 (Native)
Parent Process: launchd [371]
Responsible: BitSharesX [48656]
User ID: 501
Date/Time: 2014-08-28 19:45:19.195 -0400
OS Version: Mac OS X 10.9.3 (13D65)
Report Version: 11
Anonymous UUID: AF344F7C-B3F6-3789-440C-0799A13448F7
Sleep/Wake UUID: 41812ABC-D275-457D-810C-E646104676E9
Crashed Thread: 5
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0xfffffffffffffd40
Here's what's going on for me:
I've been able to get stable versions of the client running on both a windows machine and a mac machine without importing a wallet backup. If I upload my latest manual backup (which is from 8.26) and rescan the block chain, my balance are over 50% less than what they should be.
This is where it gets interesting, my last transaction was yesterday (8.27) at 4:46:28 PM EDT I did not get the chance to do a manual backup at this point. The reason I know this is when I retain the "default" folder in its current location and launch via "reset database". I can see all my transaction up to the point in which the client began crashing for me while the blockchain is syncing. I was even able to pull screenshots of everything to see all the transactions that were made. I'm able to get all the blocks synced and up to date (only by removing the default folder and letting the blockchain catch up); once I re-insert the "default" folder and rescan the transactions, the wallet crashes.
Now, I understand this isn't what you're supposed to do and I didn't realize until after I mentioned it and BM said not too... I was running the same wallet on multiple machines and doing market trades with multiple accounts within the wallet. I think this may have something to do with what's going on.
My questions is: what information do I need in order to "unwind" all those transactions and get it back to where I believe it to be correct. I also may have had some open orders, but I'm not certain.
TLDR; Balances way off with manual backup; client crashes with [as close to] "correct balance" [as I can tell] with 'default' backup.