226
Technical Support / Re: 0.8.1 Crashing
« on: April 23, 2015, 12:44:10 am »
Does this problem still happen for you in RC2: https://bitsharestalk.org/index.php/topic,15900.msg203941.html#msg203941
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
229
Technical Support / Re: wallet_regenerate_keys in wallet with multiple accounts
« on: April 22, 2015, 09:47:25 pm »I'm trying wallet_regenerate_keys on an account in a wallet, but it keeps crashing. Any hints? Redacted error below:Code: [Select]>>> wallet_regenerate_keys XXX 10500
Backing up wallet...
Wallet automatically backed up to: XXX-before_key_regeneration.json
This may take a while...
Regenerating wallet child keys and importing into account: XXX
10 assert_exception: Assert Exception
*account_name == account_record->name: That key already belongs to a local account with a different name!
{"account_record":{"index":X,"id":X,"name":"[b]NOT THE NAME I'M REGENERATING[/b]","public_data":null,"owner_key":"XXX","active_key_history":[["XXX"]],"registration_date":"XXX","last_update":"XXX","delegate_info":null,"meta_data":{"type":"public_account","data":""},"is_my_account":true,"approved":0,"is_favorite":true,"block_production_enabled":false,"last_used_gen_sequence":0,"private_data":null},"account_name":"[b]THE NAME I'M REGENERATING[/b]"}
th_a wallet.cpp:1667 import_private_key
{"account_name":"[b]THE NAME I'M REGENERATING[/b]","create_account":false}
th_a wallet.cpp:1689 import_private_key
10 assert_exception: Assert Exception
*account_name == blockchain_account_record->name: That key already belongs to a registered account with a different name!
{"blockchain_account_record":{"id":X,"name":"[b]ANOTHER DIFFERENT NAME[/b]","public_data":{"version":"0.8.1","slate_id":X},"owner_key":"XXX","active_key_history":[["XXX"]],"registration_date":"X","last_update":"X","delegate_info":{"votes_for":XXX,"pay_rate":X,"signing_key_history":[[XXX],"last_block_num_produced":XXX,"next_secret_hash":"XXX","pay_balance":XXX,"total_paid":XXX,"total_burned":X,"blocks_produced":XXX,"blocks_missed":XXX},"meta_data":{"type":"titan_account","data":""}},"account_name":"[b]THE NAME I'M REGENERATING[/b]"}
th_a wallet.cpp:1631 import_private_key
{"account_name":"[b]THE NAME I'M REGENERATING[/b]","create_account":false}
th_a wallet.cpp:1689 import_private_key
10 assert_exception: Assert Exception
*account_name == account_record->name: That key already belongs to a local account with a different name!
{"account_record":{"index":X,"id":XX,"name":"[b]YET ANOTHER DIFFERENT NAME[/b]","public_data":{"gravatarID":""},"owner_key":"XXX","active_key_history":[["XXXX"]],"registration_date":"X","last_update":"X","delegate_info":null,"meta_data":{"type":"titan_account","data":""},"is_my_account":true,"approved":0,"is_favorite":true,"block_production_enabled":false,"last_used_gen_sequence":X,"private_data":null},"account_name":"[b]THE NAME I'M REGENERATING[/b]"}
th_a wallet.cpp:1667 import_private_key
{"account_name":"[b]THE NAME I'M REGENERATING[/b]","create_account":false}
th_a wallet.cpp:1689 import_private_key
Segmentation fault (core dumped)
Can you run in a debugger and get a stack trace of the crash?
230
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 22, 2015, 08:35:21 pm »I agree with this..Should be fixed in final release.Is there going to be another RC rolled before release then? It's not really a good final release candidate if there are known crashes...
While I understand we're still dealing with 0.x releases, starting to formalize the release procedure might be a good idea.
Yea, we will do an RC2 soon and hardfork will be delayed.
231
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 22, 2015, 03:48:48 pm »Getting "invalid asset amount (35005)" when attempting to short bitUSDCode: [Select]getStackTrace@app.js:35:5176
○ request@app.js:45:8571
○ market_submit_short@app.js:46:7953
○ post_short@app.js:43:47902
○ app.js:43:46465
○ confirm_order@app.js:43:46529
○ confirm_order@app.js:36:27294
○ app.js:10:7986
○ e@app.js:10:14415
○ $eval@app.js:6:83428
○ $apply@app.js:6:83659
○ app.js:10:14472
○ dispatch@app.js:3:14478
○ handle@app.js:3:11253
35005 invalid_asset_amount: invalid asset amount
{"share_string":"430068.550050000020","max_rhs_size":5}
bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi
{"share_string":"430068.550050000020","precision":100000}
bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi
{"amount":"430068.550050000020"}
bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string
{"amount":"430068.550050000020","symbol":"BTS"}
bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset
{"from_account_name":"mattjohnson","real_quantity_xts":"430068.550050000020","quote_symbol":"USD","apr":"0.100000000000","collateral_symbol":"BTS","price_limit":"0.004424778761","sign":true}
bitshares wallet.cpp:3610 bts::wallet::wallet::submit_short
{}
bitshares common_api_client.cpp:5347 bts::rpc_stubs::common_api_client::wallet_market_submit_short
Should be fixed in final release.
232
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 22, 2015, 03:48:34 pm »Right after the replay, BitShares encountered an exception. I relaunched it and got another:Code: [Select]Process: BitShares [4396]
Path: /Applications/BitShares.app/Contents/MacOS/BitShares
Identifier: org.bitshares.BitShares
Version: .. (..)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: BitShares [4396]
Date/Time: 2015-04-20 21:30:07.859 -0500
OS Version: Mac OS X 10.10.2
Report Version: 11
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000058
VM Regions Near 0x58:
-->
__TEXT 00000001040b4000-0000000105ed6000 [ 30.1M] r-x/rwx SM=COW /Applications/BitShares.app/Contents/MacOS/BitShares
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 org.qt-project.QtCore 0x0000000109e6fc3e QMetaObject::activate(QObject*, int, int, void**) + 62
1 org.qt-project.QtNetwork 0x0000000109b4e2cc QNetworkReply::downloadProgress(long long, long long) + 76
2 org.qt-project.QtNetwork 0x0000000109ac8770 QNetworkReplyHttpImplPrivate::replyDownloadData(QByteArray) + 1280
3 org.qt-project.QtNetwork 0x0000000109b4ead4 QNetworkReplyHttpImpl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 1828
4 org.qt-project.QtCore 0x0000000109e69393 QObject::event(QEvent*) + 755
5 org.qt-project.QtWidgets 0x000000010686932b QApplicationPrivate::notify_helper(QObject*, QEvent*) + 251
6 org.qt-project.QtWidgets 0x000000010686c648 QApplication::notify(QObject*, QEvent*) + 8136
7 org.bitshares.BitShares 0x00000001040ebc6e BitSharesApp::notify(QObject*, QEvent*) + 14
8 org.qt-project.QtCore 0x0000000109e3ea5b QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 971
Now I launched it for the third time, no problems logging in! A fleeting bug of some sort. On to more testing...
I had a similar experience. Crashed 3-4 times then made it through the replay to the login screen.
Same here, crashed 2-3 times.
QT wallet is crashing for me. Here's the console log after it did it's block replay. Re-running the program causes the same exception apart from the initial "successfully replayed / blockchain size changed" lines.
Loading config from file: /home/chris/.BitShares/config.json
Using built-in blockchain checkpoints
Initializing state from built-in genesis file
Successfully replayed 2342769 blocks in 1840 seconds.
Blockchain size changed from 1308MiB to 1310MiB.
/index.html
/css/app.css
/js/app.js
/locale-en.json
/img/xts-logo-xl-white-shadow.png
/img/logo-ico.svg
/img/xt-background.jpg
/webfonts/Roboto-Regular-webfont.woff
/webfonts/fontawesome-webfont.woff
QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
/webfonts/Roboto-Regular-webfont.ttf
QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
/webfonts/Roboto-Regular-webfont.svg
QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
fish: Job 1, “./programs/qt_wallet/bin/BitShares ” terminated by signal SIGSEGV (Address boundary error)
Should be fixed in final release.
233
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 21, 2015, 09:32:17 pm »I've downloaded the 0.9.0-RC1 on my Windows 7 test machine and am having numerous problems.
It crashed several times and froze and had to be closed several times, but finally it loaded and synced.
But there are 21 accounts at the Dashboard page, 19 of them not mine! Some of them appear to be accounts that I sent 0.5BTS to when I was sending to newbies to register. Others, I have no idea, and they aren't registered.
And now the client says "Severe network problems" and is not syncing even though on my main machine with the 0.8.0 version there is no network problem.
Shut down and restarted again, twice. Same thing. "Severe network problems", not syncing, and still al the extra accounts at Dashboard.
I can't get to the console for information because the 21 accounts go below the page, and I can't scroll down past them to "Advanced".
This sounds like a possible side-effect of the wallet db upgrade on first open--has your situation changed at all?
Final release should have a fix for the extraneous accounts showing up.
234
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 21, 2015, 09:31:46 pm »4.) >Exchange>%market> Wallet occasionally crashes on selecting a market
There have been reports of this for a long time, but we haven't been able to track it down yet: https://github.com/BitShares/bitshares/issues/1477
It would be extremely helpful if anyone could get a stack trace of this crash.
235
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 21, 2015, 05:53:47 pm »Does "wallet_publish_price_feed" require a float/double price or a satoshi/larimer?
All decimal amounts/prices should be input as strings now.
236
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 21, 2015, 03:46:28 pm »I've downloaded the 0.9.0-RC1 on my Windows 7 test machine and am having numerous problems.
It crashed several times and froze and had to be closed several times, but finally it loaded and synced.
But there are 21 accounts at the Dashboard page, 19 of them not mine! Some of them appear to be accounts that I sent 0.5BTS to when I was sending to newbies to register. Others, I have no idea, and they aren't registered.
And now the client says "Severe network problems" and is not syncing even though on my main machine with the 0.8.0 version there is no network problem.
Shut down and restarted again, twice. Same thing. "Severe network problems", not syncing, and still al the extra accounts at Dashboard.
I can't get to the console for information because the 21 accounts go below the page, and I can't scroll down past them to "Advanced".
This sounds like a possible side-effect of the wallet db upgrade on first open--has your situation changed at all?
237
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 21, 2015, 03:32:16 pm »It looks like you have a local account or contact in your wallet named gatewayclient with different keys compared to the gatewayclient registered on the blockchain. You might have to use `wallet_account_rename` or `wallet_add_contact` to rename the local entry.
Hmmm, that's very odd. I do appear to have an unregistered account with that name, but I cannot rename it:Code: [Select]default (unlocked) >>> wallet_rename_account gatewayclient oisdjfosfjsf
20032 key_already_registered: key belongs to other account
or retract it:Code: [Select]default (unlocked) >>> wallet_account_retract gatewayclient monsterer
20025 duplicate_account_name: duplicate account name
{"*local_account":{"index":190,"id":0,"name":"gatewayclient","public_data":null,"owner_key":"BTS
6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB","active_key_history":[["2015-01-12T08:58:01","BT
S6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB"]],"registration_date":"1970-01-01T00:00:00","la
st_update":"2015-01-12T08:58:01","last_child_key_index":0,"block_production_enabled":false,"custom_d
ata":{},"approved":0},"*chain_account":{"id":32380,"name":"gatewayclient","public_data":null,"owner_
key":"BTS5AfzawTGh4gmoDBmxgBgAn38UeiDLy2e8VdB6dgn6n3iE2SzHq","active_key_history":[["2015-01-14T08:4
5:50","BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB"],["2015-01-15T20:53:00","BTS5zU8LZUVPT
DV262RrNGoHHkyi7UCSj6t98e45z7YXeLaNN7r4H"]],"registration_date":"2015-01-14T08:45:50","last_update":
"2015-01-15T20:53:00","meta_data":{"type":"titan_account","data":""}}}
th_a wallet.cpp:1332 bts::wallet::wallet::get_account
{"account_name":"gatewayclient"}
th_a wallet.cpp:1345 bts::wallet::wallet::get_account
{"account_to_retract":"gatewayclient","pay_from_account":"monsterer","sign":true}
th_a wallet.cpp:3451 bts::wallet::wallet::retract_account
{}
th_a common_api_client.cpp:6310 bts::rpc_stubs::common_api_client::wallet_account_retract
{"command":"wallet_account_retract"}
th_a cli.cpp:626 bts::cli::detail::cli_impl::execute_command
What can I do?
Hmm actually looking closer, it looks like the same account, but your local version looks like:
owner_key: BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB
active_keys:
BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB
showing up as unregistered
And the blockchain version looks like:
owner_key: BTS5AfzawTGh4gmoDBmxgBgAn38UeiDLy2e8VdB6dgn6n3iE2SzHq
active_keys:
BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB
BTS5zU8LZUVPTDV262RrNGoHHkyi7UCSj6t98e45z7YXeLaNN7r4H
Do you have the private key for BTS5AfzawTGh4gmoDBmxgBgAn38UeiDLy2e8VdB6dgn6n3iE2SzHq ?
Can you try "scan 0 1" and see if your local account gets updated to be consistent with the blockchain?
238
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 21, 2015, 03:04:02 pm »Code: [Select]{\"jsonrpc\":\"2\",\"id\":1,\"method\":\"wallet_transfer\",\"params\":[\"0.0242\",\"USD\",\"gatewaytest\",\"gatewayclient\",\"mX: buy USD\",\"vote_recommended\"]}
Results in this error:Quoteresult "{\"id\":1,\"error\":{\"message\":\"duplicate account name (20025)\\n\\n\\n\\n\\n\\n\",\"detail\":\"20025 duplicate_account_name: duplicate account name\\n\\n {\\\"*recipient_account\\\":{\\\"index\\\":190,\\\"id\\\":0,\\\"name\\\":\\\"gatewayclient\\\",\\\"public_data\\\":null,\\\"owner_key\\\":\\\"BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB\\\",\\\"active_key_history\\\":[[\\\"2015-01-12T08:58:01\\\",\\\"BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB\\\"]],\\\"registration_date\\\":\\\"1970-01-01T00:00:00\\\",\\\"last_update\\\":\\\"2015-01-12T08:58:01\\\",\\\"last_child_key_index\\\":0,\\\"block_production_enabled\\\":false,\\\"custom_data\\\":{},\\\"approved\\\":0},\\\"*registered_recipient_account\\\":{\\\"id\\\":32380,\\\"name\\\":\\\"gatewayclient\\\",\\\"public_data\\\":null,\\\"owner_key\\\":\\\"BTS5AfzawTGh4gmoDBmxgBgAn38UeiDLy2e8VdB6dgn6n3iE2SzHq\\\",\\\"active_key_history\\\":[[\\\"2015-01-14T08:45:50\\\",\\\"BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskB\\\"],[\\\"2015-01-15T20:53:00\\\",\\\"BTS5zU8LZUVPTDV262RrNGoHHkyi7UCSj6t98e45z7YXeLaNN7r4H\\\"]],\\\"registration_date\\\":\\\"2015-01-14T08:45:50\\\",\\\"last_update\\\":\\\"2015-01-15T20:53:00\\\",\\\"meta_data\\\":{\\\"type\\\":\\\"titan_account\\\",\\\"data\\\":\\\"\\\"}}}\\n th_a wallet.cpp:146 bts::wallet::detail::wallet_impl::deposit_from_transaction\\n\\n {\\\"transaction\\\":{\\\"expiration\\\":\\\"2015-04-21T15:37:43\\\",\\\"operations\\\":[{\\\"type\\\":\\\"withdraw_op_type\\\",\\\"data\\\":{\\\"balance_id\\\":\\\"BTS2omvvwP4A5cpxmT9K9WCm4YpaSewDaXXA\\\",\\\"amount\\\":13,\\\"claim_input_data\\\":\\\"\\\"}},{\\\"type\\\":\\\"withdraw_op_type\\\",\\\"data\\\":{\\\"balance_id\\\":\\\"BTSEUzXxEeuKR6eLTWBexdQqcnRxG6XVeBo7\\\",\\\"amount\\\":242,\\\"claim_input_data\\\":\\\"\\\"}}],\\\"signatures\\\":[]},\\\"amount\\\":{\\\"amount\\\":242,\\\"asset_id\\\":22},\\\"sender\\\":{\\\"index\\\":128,\\\"id\\\":32192,\\\"name\\\":\\\"gatewaytest\\\",\\\"public_data\\\":{\\\"gui_data\\\":{\\\"website\\\":\\\"\\\"}},\\\"owner_key\\\":\\\"BTS5dvyrpghWB9vmcZtcJVWJtYhLCQ4S8ptriskuLv45Qqi4FDe8X\\\",\\\"active_key_history\\\":[[\\\"2015-01-09T16:26:50\\\",\\\"BTS8mxPVLbNLbVqiy9Lk3woFdtFU6xzhMJhY4NRbyE3YuNJUL85YF\\\"],[\\\"2015-01-17T19:52:30\\\",\\\"BTS5SekcLhriLeAhtLrnNhoBjy4tqSgacgnWm95WB5x28sau1DsoX\\\"]],\\\"registration_date\\\":\\\"2015-01-09T16:26:50\\\",\\\"last_update\\\":\\\"2015-01-17T19:52:30\\\",\\\"meta_data\\\":{\\\"type\\\":\\\"titan_account\\\",\\\"data\\\":\\\"\\\"},\\\"last_child_key_index\\\":0,\\\"block_production_enabled\\\":false,\\\"custom_data\\\":{},\\\"approved\\\":0},\\\"recipient\\\":{\\\"index\\\":2256,\\\"contact_type\\\":\\\"account_name\\\",\\\"data\\\":\\\"gatewayclient\\\",\\\"label\\\":\\\"gatewayclient\\\",\\\"custom_data\\\":{}},\\\"memo\\\":\\\"mX: buy USD\\\"}\\n th_a wallet.cpp:204 bts::wallet::detail::wallet_impl::deposit_from_transaction\\n\\n {\\\"amount\\\":{\\\"amount\\\":242,\\\"asset_id\\\":22},\\\"sender_account_name\\\":\\\"gatewaytest\\\",\\\"generic_recipient\\\":\\\"gatewayclient\\\",\\\"memo\\\":\\\"mX: buy USD\\\",\\\"strategy\\\":\\\"vote_recommended\\\",\\\"sign\\\":true}\\n th_a wallet.cpp:2830 bts::wallet::wallet::transfer\\n\\n {\\\"amount_to_transfer\\\":\\\"0.0242\\\",\\\"asset_symbol\\\":\\\"USD\\\",\\\"from_account_name\\\":\\\"gatewaytest\\\",\\\"recipient\\\":\\\"gatewayclient\\\",\\\"memo_message\\\":\\\"mX: buy USD\\\",\\\"strategy\\\":\\\"vote_recommended\\\"}\\n th_a wallet_api.cpp:322 bts::client::detail::client_impl::wallet_transfer\\n\\n {}\\n th_a common_api_client.cpp:3845 bts::rpc_stubs::common_api_client::wallet_transfer\",\"code\":20025}}" string
This used to work in the previous version - it's a simple USD transfer from gatewaytest to gatewayclient.
It looks like you have a local account or contact in your wallet named gatewayclient with different keys compared to the gatewayclient registered on the blockchain. You might have to use `wallet_account_rename` or `wallet_add_contact` to rename the local entry.
239
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 21, 2015, 03:01:09 pm »Any particular reason for the seemly arbitrary renaming of members inside the JSON returned by get_asset?
issuer_account_id -> issuer_id
current_share_supply -> current_supply
maximum_share_supply -> max_supply
etc?
Sorry, I've added a note about this in the API changes.
No real external reason for these particular renames. I believe I was renaming them to force compiler errors at all usages while I was writing the advanced UIA code.
240
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 21, 2015, 02:58:35 pm »Right after the replay, BitShares encountered an exception. I relaunched it and got another:Code: [Select]Process: BitShares [4396]
Path: /Applications/BitShares.app/Contents/MacOS/BitShares
Identifier: org.bitshares.BitShares
Version: .. (..)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: BitShares [4396]
Date/Time: 2015-04-20 21:30:07.859 -0500
OS Version: Mac OS X 10.10.2
Report Version: 11
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000058
VM Regions Near 0x58:
-->
__TEXT 00000001040b4000-0000000105ed6000 [ 30.1M] r-x/rwx SM=COW /Applications/BitShares.app/Contents/MacOS/BitShares
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 org.qt-project.QtCore 0x0000000109e6fc3e QMetaObject::activate(QObject*, int, int, void**) + 62
1 org.qt-project.QtNetwork 0x0000000109b4e2cc QNetworkReply::downloadProgress(long long, long long) + 76
2 org.qt-project.QtNetwork 0x0000000109ac8770 QNetworkReplyHttpImplPrivate::replyDownloadData(QByteArray) + 1280
3 org.qt-project.QtNetwork 0x0000000109b4ead4 QNetworkReplyHttpImpl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 1828
4 org.qt-project.QtCore 0x0000000109e69393 QObject::event(QEvent*) + 755
5 org.qt-project.QtWidgets 0x000000010686932b QApplicationPrivate::notify_helper(QObject*, QEvent*) + 251
6 org.qt-project.QtWidgets 0x000000010686c648 QApplication::notify(QObject*, QEvent*) + 8136
7 org.bitshares.BitShares 0x00000001040ebc6e BitSharesApp::notify(QObject*, QEvent*) + 14
8 org.qt-project.QtCore 0x0000000109e3ea5b QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 971
Now I launched it for the third time, no problems logging in! A fleeting bug of some sort. On to more testing...
I had a similar experience. Crashed 3-4 times then made it through the replay to the login screen.
On the login screen, unlocking the wallet causes the program to hang at the loader. Wiping the app data and resetting the chain ended in a crashing scenario like above which eventually resolves but then the hanging issue happens.
OS X isn't stable but it sounds like this release is more stable for Windows users. That's a good sign at least.
edit: let it hang logging for about 10 minutes and it eventually authed me.
Wallet database will upgrade once on first open and can take some time--I've added a note to the changelog.
