0 Members and 1 Guest are viewing this topic.
I have 4 GB of ram and I don't have a swap file, but how the heck much ram does this thing need to be happy???Also I have an update for you. After my last posting I just started it using screen then performed a get_info and the let it run over night.30 minutes after starting screen...Code: [Select]default (unlocked) >>> get_info{ "blockchain_head_block_num": 1248189, "blockchain_head_block_age": "19 weeks old", "blockchain_head_block_timestamp": "2014-12-12T23:37:50", "blockchain_head_block_id": "b1eb0fa8092070dd785dbbf27572604aa2ae7bd6", "blockchain_average_delegate_participation": "0.01 %", "blockchain_share_supply": "2,498,315,210.15240 BTS", "blockchain_blocks_left_in_round": 70, "blockchain_next_round_time": "at least 12 minutes in the future", "blockchain_next_round_timestamp": "2015-04-21T19:37:00", "client_data_dir": "/home/dev/.BitShares", "client_version": "0.9.0-rc1", "network_num_connections": 18, "network_num_connections_max": 200, "network_chain_downloader_running": false, "network_chain_downloader_blocks_remaining": null, "ntp_time": "2015-04-21T19:25:24", "ntp_time_error": -0.015821000000000002, "wallet_open": true, "wallet_unlocked": true, "wallet_unlocked_until": "8 days in the future", "wallet_unlocked_until_timestamp": "2015-04-29T09:30:53", "wallet_last_scanned_block_timestamp": null, "wallet_scan_progress": "100.00 %", "wallet_block_production_enabled": false, "wallet_next_block_production_time": null, "wallet_next_block_production_timestamp": null}Then just a bit ago...Code: [Select]default (unlocked) >>> get_info{ "blockchain_head_block_num": 1248189, "blockchain_head_block_age": "19 weeks old", "blockchain_head_block_timestamp": "2014-12-12T23:37:50", "blockchain_head_block_id": "b1eb0fa8092070dd785dbbf27572604aa2ae7bd6", "blockchain_average_delegate_participation": "0.01 %", "blockchain_share_supply": "2,498,315,210.15240 BTS", "blockchain_blocks_left_in_round": 70, "blockchain_next_round_time": "at least 12 minutes in the future", "blockchain_next_round_timestamp": "2015-04-22T18:57:50", "client_data_dir": "/home/dev/.BitShares", "client_version": "0.9.0-rc1", "network_num_connections": 14, "network_num_connections_max": 200, "network_chain_downloader_running": false, "network_chain_downloader_blocks_remaining": null, "ntp_time": "2015-04-22T18:46:11", "ntp_time_error": 0.188475, "wallet_open": true, "wallet_unlocked": true, "wallet_unlocked_until": "7 days in the future", "wallet_unlocked_until_timestamp": "2015-04-29T09:30:53", "wallet_last_scanned_block_timestamp": null, "wallet_scan_progress": "100.00 %", "wallet_block_production_enabled": false, "wallet_next_block_production_time": null, "wallet_next_block_production_timestamp": null}Any particular reason it would be stuck at that block?Also I'm thinking the memory leak issue might be something else. I let it run all night under screen and the cli is properly responsive still. So maybe not CLI, but maybe something in the syncing process. Since it hasn't synced anything all night???
default (unlocked) >>> get_info{ "blockchain_head_block_num": 1248189, "blockchain_head_block_age": "19 weeks old", "blockchain_head_block_timestamp": "2014-12-12T23:37:50", "blockchain_head_block_id": "b1eb0fa8092070dd785dbbf27572604aa2ae7bd6", "blockchain_average_delegate_participation": "0.01 %", "blockchain_share_supply": "2,498,315,210.15240 BTS", "blockchain_blocks_left_in_round": 70, "blockchain_next_round_time": "at least 12 minutes in the future", "blockchain_next_round_timestamp": "2015-04-21T19:37:00", "client_data_dir": "/home/dev/.BitShares", "client_version": "0.9.0-rc1", "network_num_connections": 18, "network_num_connections_max": 200, "network_chain_downloader_running": false, "network_chain_downloader_blocks_remaining": null, "ntp_time": "2015-04-21T19:25:24", "ntp_time_error": -0.015821000000000002, "wallet_open": true, "wallet_unlocked": true, "wallet_unlocked_until": "8 days in the future", "wallet_unlocked_until_timestamp": "2015-04-29T09:30:53", "wallet_last_scanned_block_timestamp": null, "wallet_scan_progress": "100.00 %", "wallet_block_production_enabled": false, "wallet_next_block_production_time": null, "wallet_next_block_production_timestamp": null}
default (unlocked) >>> get_info{ "blockchain_head_block_num": 1248189, "blockchain_head_block_age": "19 weeks old", "blockchain_head_block_timestamp": "2014-12-12T23:37:50", "blockchain_head_block_id": "b1eb0fa8092070dd785dbbf27572604aa2ae7bd6", "blockchain_average_delegate_participation": "0.01 %", "blockchain_share_supply": "2,498,315,210.15240 BTS", "blockchain_blocks_left_in_round": 70, "blockchain_next_round_time": "at least 12 minutes in the future", "blockchain_next_round_timestamp": "2015-04-22T18:57:50", "client_data_dir": "/home/dev/.BitShares", "client_version": "0.9.0-rc1", "network_num_connections": 14, "network_num_connections_max": 200, "network_chain_downloader_running": false, "network_chain_downloader_blocks_remaining": null, "ntp_time": "2015-04-22T18:46:11", "ntp_time_error": 0.188475, "wallet_open": true, "wallet_unlocked": true, "wallet_unlocked_until": "7 days in the future", "wallet_unlocked_until_timestamp": "2015-04-29T09:30:53", "wallet_last_scanned_block_timestamp": null, "wallet_scan_progress": "100.00 %", "wallet_block_production_enabled": false, "wallet_next_block_production_time": null, "wallet_next_block_production_timestamp": null}
Quote from: SmileyChris on April 22, 2015, 07:29:13 pmQuote from: vikram on April 22, 2015, 03:48:48 pmShould 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.I agree with this..
Quote from: vikram on April 22, 2015, 03:48:48 pmShould 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.
Should be fixed in final release.
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:1125335005 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
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:1125335005 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
Quote from: robrigo on April 21, 2015, 04:06:20 amQuote from: roadscape on April 21, 2015, 02:36:57 amRight after the replay, BitShares encountered an exception. I relaunched it and got another:Code: [Select]Process: BitShares [4396]Path: /Applications/BitShares.app/Contents/MacOS/BitSharesIdentifier: org.bitshares.BitSharesVersion: .. (..)Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: BitShares [4396]Date/Time: 2015-04-20 21:30:07.859 -0500OS Version: Mac OS X 10.10.2Report Version: 11Crashed Thread: 0 Dispatch queue: com.apple.main-threadException Type: EXC_BAD_ACCESS (SIGSEGV)Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000058VM Regions Near 0x58:--> __TEXT 00000001040b4000-0000000105ed6000 [ 30.1M] r-x/rwx SM=COW /Applications/BitShares.app/Contents/MacOS/BitSharesThread 0 Crashed:: Dispatch queue: com.apple.main-thread0 org.qt-project.QtCore 0x0000000109e6fc3e QMetaObject::activate(QObject*, int, int, void**) + 621 org.qt-project.QtNetwork 0x0000000109b4e2cc QNetworkReply::downloadProgress(long long, long long) + 762 org.qt-project.QtNetwork 0x0000000109ac8770 QNetworkReplyHttpImplPrivate::replyDownloadData(QByteArray) + 12803 org.qt-project.QtNetwork 0x0000000109b4ead4 QNetworkReplyHttpImpl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 18284 org.qt-project.QtCore 0x0000000109e69393 QObject::event(QEvent*) + 7555 org.qt-project.QtWidgets 0x000000010686932b QApplicationPrivate::notify_helper(QObject*, QEvent*) + 2516 org.qt-project.QtWidgets 0x000000010686c648 QApplication::notify(QObject*, QEvent*) + 81367 org.bitshares.BitShares 0x00000001040ebc6e BitSharesApp::notify(QObject*, QEvent*) + 148 org.qt-project.QtCore 0x0000000109e3ea5b QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 971Now 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.
Quote from: roadscape on April 21, 2015, 02:36:57 amRight after the replay, BitShares encountered an exception. I relaunched it and got another:Code: [Select]Process: BitShares [4396]Path: /Applications/BitShares.app/Contents/MacOS/BitSharesIdentifier: org.bitshares.BitSharesVersion: .. (..)Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: BitShares [4396]Date/Time: 2015-04-20 21:30:07.859 -0500OS Version: Mac OS X 10.10.2Report Version: 11Crashed Thread: 0 Dispatch queue: com.apple.main-threadException Type: EXC_BAD_ACCESS (SIGSEGV)Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000058VM Regions Near 0x58:--> __TEXT 00000001040b4000-0000000105ed6000 [ 30.1M] r-x/rwx SM=COW /Applications/BitShares.app/Contents/MacOS/BitSharesThread 0 Crashed:: Dispatch queue: com.apple.main-thread0 org.qt-project.QtCore 0x0000000109e6fc3e QMetaObject::activate(QObject*, int, int, void**) + 621 org.qt-project.QtNetwork 0x0000000109b4e2cc QNetworkReply::downloadProgress(long long, long long) + 762 org.qt-project.QtNetwork 0x0000000109ac8770 QNetworkReplyHttpImplPrivate::replyDownloadData(QByteArray) + 12803 org.qt-project.QtNetwork 0x0000000109b4ead4 QNetworkReplyHttpImpl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 18284 org.qt-project.QtCore 0x0000000109e69393 QObject::event(QEvent*) + 7555 org.qt-project.QtWidgets 0x000000010686932b QApplicationPrivate::notify_helper(QObject*, QEvent*) + 2516 org.qt-project.QtWidgets 0x000000010686c648 QApplication::notify(QObject*, QEvent*) + 81367 org.bitshares.BitShares 0x00000001040ebc6e BitSharesApp::notify(QObject*, QEvent*) + 148 org.qt-project.QtCore 0x0000000109e3ea5b QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 971Now 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.
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/BitSharesIdentifier: org.bitshares.BitSharesVersion: .. (..)Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: BitShares [4396]Date/Time: 2015-04-20 21:30:07.859 -0500OS Version: Mac OS X 10.10.2Report Version: 11Crashed Thread: 0 Dispatch queue: com.apple.main-threadException Type: EXC_BAD_ACCESS (SIGSEGV)Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000058VM Regions Near 0x58:--> __TEXT 00000001040b4000-0000000105ed6000 [ 30.1M] r-x/rwx SM=COW /Applications/BitShares.app/Contents/MacOS/BitSharesThread 0 Crashed:: Dispatch queue: com.apple.main-thread0 org.qt-project.QtCore 0x0000000109e6fc3e QMetaObject::activate(QObject*, int, int, void**) + 621 org.qt-project.QtNetwork 0x0000000109b4e2cc QNetworkReply::downloadProgress(long long, long long) + 762 org.qt-project.QtNetwork 0x0000000109ac8770 QNetworkReplyHttpImplPrivate::replyDownloadData(QByteArray) + 12803 org.qt-project.QtNetwork 0x0000000109b4ead4 QNetworkReplyHttpImpl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 18284 org.qt-project.QtCore 0x0000000109e69393 QObject::event(QEvent*) + 7555 org.qt-project.QtWidgets 0x000000010686932b QApplicationPrivate::notify_helper(QObject*, QEvent*) + 2516 org.qt-project.QtWidgets 0x000000010686c648 QApplication::notify(QObject*, QEvent*) + 81367 org.bitshares.BitShares 0x00000001040ebc6e BitSharesApp::notify(QObject*, QEvent*) + 148 org.qt-project.QtCore 0x0000000109e3ea5b QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 971Now I launched it for the third time, no problems logging in! A fleeting bug of some sort. On to more testing...
Process: BitShares [4396]Path: /Applications/BitShares.app/Contents/MacOS/BitSharesIdentifier: org.bitshares.BitSharesVersion: .. (..)Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: BitShares [4396]Date/Time: 2015-04-20 21:30:07.859 -0500OS Version: Mac OS X 10.10.2Report Version: 11Crashed Thread: 0 Dispatch queue: com.apple.main-threadException Type: EXC_BAD_ACCESS (SIGSEGV)Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000058VM Regions Near 0x58:--> __TEXT 00000001040b4000-0000000105ed6000 [ 30.1M] r-x/rwx SM=COW /Applications/BitShares.app/Contents/MacOS/BitSharesThread 0 Crashed:: Dispatch queue: com.apple.main-thread0 org.qt-project.QtCore 0x0000000109e6fc3e QMetaObject::activate(QObject*, int, int, void**) + 621 org.qt-project.QtNetwork 0x0000000109b4e2cc QNetworkReply::downloadProgress(long long, long long) + 762 org.qt-project.QtNetwork 0x0000000109ac8770 QNetworkReplyHttpImplPrivate::replyDownloadData(QByteArray) + 12803 org.qt-project.QtNetwork 0x0000000109b4ead4 QNetworkReplyHttpImpl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 18284 org.qt-project.QtCore 0x0000000109e69393 QObject::event(QEvent*) + 7555 org.qt-project.QtWidgets 0x000000010686932b QApplicationPrivate::notify_helper(QObject*, QEvent*) + 2516 org.qt-project.QtWidgets 0x000000010686c648 QApplication::notify(QObject*, QEvent*) + 81367 org.bitshares.BitShares 0x00000001040ebc6e BitSharesApp::notify(QObject*, QEvent*) + 148 org.qt-project.QtCore 0x0000000109e3ea5b QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 971
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.jsonUsing built-in blockchain checkpointsInitializing state from built-in genesis fileSuccessfully 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.woffQNetworkReplyImplPrivate::error: Internal problem, this method must only be called once./webfonts/Roboto-Regular-webfont.ttfQNetworkReplyImplPrivate::error: Internal problem, this method must only be called once./webfonts/Roboto-Regular-webfont.svgQNetworkReplyImplPrivate::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)
Continuing wallet upgrade...Repairing key record 11746MEM CPU 555.43 MEM 4814328 MAXMEM 4814328 STALE 1721
Quote from: vikram on April 21, 2015, 09:31:46 pmQuote from: Xeldal on April 21, 2015, 03:50:53 pm4.) >Exchange>%market> Wallet occasionally crashes on selecting a marketThere 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/1477It would be extremely helpful if anyone could get a stack trace of this crash.Yes it does it and it is indeed randomly ,from what I can tell ( in 0.8.0). The only relatively sure [7-8 out of 10 times on 8G + regular hard drive] way to achieve/recreate it is:- Restart the client (GUI) after at least 6h of not running it. (preferably 24h+)- Go to exchange; and click on non-BTS market (so something like bitUSD:bitBTC should work) do this fast - before the Market (i.e. its graphs) has fully loaded. [edit] And no I have not let it to do crush as of late - it starts consuming memory like crazy in a matter of minutes. So I kill the process when it approaches 2G RAM.
Quote from: Xeldal on April 21, 2015, 03:50:53 pm4.) >Exchange>%market> Wallet occasionally crashes on selecting a marketThere 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/1477It would be extremely helpful if anyone could get a stack trace of this crash.
4.) >Exchange>%market> Wallet occasionally crashes on selecting a market
I wasn't able to create a short earlier. The only way I can get it to go through is if the collateral field does not contain a decimal.
Quote from: onceuponatime on April 21, 2015, 07:48:15 amI'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?
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".
Quote from: roadscape on April 21, 2015, 03:01:35 amOverall slick! Here's what I found in the GUI on OSX:Exchange page - MPA and UIA tables are not populatedMarket page - Price graphs are not showing in 'Flipped' mode - Price graph scrolls on its own when my cursor hovers over it - 'Volume' and '24hr Low/High/Change' in the upper pane all read 0 but 'Latest/Call Price' is fine - The 'Short Sell' and 'Margin Call' tables also get stuck to my cursor. The Buy/Sell tables don't seem to exhibit this behaviorSuggestions for 1280 x 800 display - Can the price graph be shrunk vertically by 25% or so? I can't see the whole depth graph without scrolling. - Can the Order History pane be widened a little? It requires horizontal scrolling and feels a bit cramped, especially in 'My Order History'Also, I restarted the client and got another exception. I launched it once more and it runs fine again.ninja edit:I like the new graphs.. big improvement! Especially with the 'All-time' view which seems to work now! The issue I mentioned above needs to be resolved so I can get the full graph experience. Also, are tooltips in the price graph gone now, or is that a bug?It's always surprising to see the number of bugs that just appear out of nowhere on release! I'll have a look once I get home. Any values not showing are most likely related to changes in the backend client API, I only tested it with 0.8.1 and there's been some changes since. The price graph has data for 1 year now which is why the all time view "works" as you say. The tooltip should be displayed in text inside the graph window, no moving tooltip.You have a pretty low resolution screen but I'll have a look if there's anything to be done.
Overall slick! Here's what I found in the GUI on OSX:Exchange page - MPA and UIA tables are not populatedMarket page - Price graphs are not showing in 'Flipped' mode - Price graph scrolls on its own when my cursor hovers over it - 'Volume' and '24hr Low/High/Change' in the upper pane all read 0 but 'Latest/Call Price' is fine - The 'Short Sell' and 'Margin Call' tables also get stuck to my cursor. The Buy/Sell tables don't seem to exhibit this behaviorSuggestions for 1280 x 800 display - Can the price graph be shrunk vertically by 25% or so? I can't see the whole depth graph without scrolling. - Can the Order History pane be widened a little? It requires horizontal scrolling and feels a bit cramped, especially in 'My Order History'Also, I restarted the client and got another exception. I launched it once more and it runs fine again.ninja edit:I like the new graphs.. big improvement! Especially with the 'All-time' view which seems to work now! The issue I mentioned above needs to be resolved so I can get the full graph experience. Also, are tooltips in the price graph gone now, or is that a bug?
No way to do titan anymore?
Ubuntu 64bit cli version.Seems to crash after an hour or two, need to keep restarting when this happens. The only message there is "killed".This was on a fresh account that never had a previous version of bitshares before.Deleting .Bitshares folder just results in everything starting over again.Command line is extremely slow to respond and this slowness grows the longer the client is running.Command line slowness is no joke, there is always literally at least 1 second in between characters, regardless of my typing speed.I think you have a memory leak because the whole machine slowed to a crawl near the end of the last incident then became snappy again once the "killed" message appeared.Have not yet synced the block chain, been at it 2 days.Thanks for the hard work though!
Quote from: xeroc ¯\_(ツ)_/¯ on April 21, 2015, 05:50:09 pmDoes "wallet_publish_price_feed" require a float/double price or a satoshi/larimer?All decimal amounts/prices should be input as strings now.
Does "wallet_publish_price_feed" require a float/double price or a satoshi/larimer?
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:1125335005 invalid_asset_amount: invalid asset amount {"share_string":"2173.562540000000","max_rhs_size":5} bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi {"share_string":"2173.562540000000","precision":100000} bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi {"amount":"2173.562540000000"} bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string {"amount":"2173.562540000000","symbol":"BTS"} bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset {"from_account_name":"enki","real_quantity_xts":"2173.562540000000","quote_symbol":"USD","apr":"0","collateral_symbol":"BTS","price_limit":"0.004600740811","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
getStackTrace@app.js:35:5176 ○ request@app.js:45:8571 ○ market_submit_bid@app.js:46:7599 ○ post_ask@app.js:43:48237 ○ app.js:43:46411 ○ 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:1125335005 invalid_asset_amount: invalid asset amount {"share_string":"0.305000000000","max_rhs_size":5} bitshares asset_record.cpp:93 bts::blockchain::asset_record::share_string_to_satoshi {"share_string":"0.305000000000","precision":100000} bitshares asset_record.cpp:109 bts::blockchain::asset_record::share_string_to_satoshi {"amount":"0.305000000000"} bitshares asset_record.cpp:114 bts::blockchain::asset_record::asset_from_string {"amount":"0.305000000000","symbol":"BTS"} bitshares chain_interface.cpp:241 bts::blockchain::chain_interface::to_ugly_asset {"from_account_name":"clayop","real_quantity":"0.305000000000","quantity_symbol":"BTS","quote_price":"3.278688524590","quote_symbol":"NOTE","sign":true} bitshares wallet.cpp:3549 bts::wallet::wallet::submit_bid {} bitshares common_api_client.cpp:5279 bts::rpc_stubs::common_api_client::wallet_market_submit_bid
Not sure if this helps, but I can recall that initially, the active_keys havebeen indentical to the owner key. Don't know which version changed that.@monsterer .. have you imported that key to the wallet or have you created it within the wallet?
just sent some NEWBIE UIA. however, the popup said I received 0.1 BTS (fee) instead of NEWBIE Amount.Edit: also got some new accounts in my wallet. some newbies I tried to help - I'd like to see a function to delete unused names
Hmm actually looking closer, it looks like the same account, but your local version looks like:owner_key: BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskBactive_keys:BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskBshowing up as unregisteredAnd the blockchain version looks like:owner_key: BTS5AfzawTGh4gmoDBmxgBgAn38UeiDLy2e8VdB6dgn6n3iE2SzHqactive_keys:BTS6hySPYfrGHLELX6TML6d8stR5wMdsoZyXPmJcBSiwHL31xaskBBTS5zU8LZUVPTDV262RrNGoHHkyi7UCSj6t98e45z7YXeLaNN7r4H
Quote from: vikram on April 21, 2015, 03:04:02 pmIt 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 oisdjfosfjsf20032 key_already_registered: key belongs to other accountor retract it:Code: [Select]default (unlocked) >>> wallet_account_retract gatewayclient monsterer20025 duplicate_account_name: duplicate account name {"*local_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},"*chain_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":""}}} 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_commandWhat can I do?
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.
default (unlocked) >>> wallet_rename_account gatewayclient oisdjfosfjsf20032 key_already_registered: key belongs to other account
default (unlocked) >>> wallet_account_retract gatewayclient monsterer20025 duplicate_account_name: duplicate account name {"*local_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},"*chain_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":""}}} 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
$ ./bitshares_client --serverLoading blockchain from: /home/delegate/.BitShares/chainLoading config from file: /home/delegate/.BitShares/config.jsonUsing built-in blockchain checkpointsInitializing state from built-in genesis filePlease be patient, this will take several minutes...Successfully replayed 2338510 blocks in 9613 seconds.Blockchain size changed from 1309MiB to 1307MiB.Starting JSON RPC server on port 9988Starting HTTP JSON RPC server on port 19988Attempting to map P2P port 1700 with UPNP...(wallet closed) >>> Segmentation fault
Code: [Select]{\"jsonrpc\":\"2\",\"id\":1,\"method\":\"wallet_transfer\",\"params\":[\"0.0242\",\"USD\",\"gatewaytest\",\"gatewayclient\",\"mX: buy USD\",\"vote_recommended\"]}Results in this error:Quote result "{\"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}}" stringThis used to work in the previous version - it's a simple USD transfer from gatewaytest to gatewayclient.
{\"jsonrpc\":\"2\",\"id\":1,\"method\":\"wallet_transfer\",\"params\":[\"0.0242\",\"USD\",\"gatewaytest\",\"gatewayclient\",\"mX: buy USD\",\"vote_recommended\"]}
result "{\"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
Any particular reason for the seemly arbitrary renaming of members inside the JSON returned by get_asset?issuer_account_id -> issuer_idcurrent_share_supply -> current_supplymaximum_share_supply -> max_supplyetc?
Quote from: roadscape on April 21, 2015, 02:36:57 amRight after the replay, BitShares encountered an exception. I relaunched it and got another:Code: [Select]Process: BitShares [4396]Path: /Applications/BitShares.app/Contents/MacOS/BitSharesIdentifier: org.bitshares.BitSharesVersion: .. (..)Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: BitShares [4396]Date/Time: 2015-04-20 21:30:07.859 -0500OS Version: Mac OS X 10.10.2Report Version: 11Crashed Thread: 0 Dispatch queue: com.apple.main-threadException Type: EXC_BAD_ACCESS (SIGSEGV)Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000058VM Regions Near 0x58:--> __TEXT 00000001040b4000-0000000105ed6000 [ 30.1M] r-x/rwx SM=COW /Applications/BitShares.app/Contents/MacOS/BitSharesThread 0 Crashed:: Dispatch queue: com.apple.main-thread0 org.qt-project.QtCore 0x0000000109e6fc3e QMetaObject::activate(QObject*, int, int, void**) + 621 org.qt-project.QtNetwork 0x0000000109b4e2cc QNetworkReply::downloadProgress(long long, long long) + 762 org.qt-project.QtNetwork 0x0000000109ac8770 QNetworkReplyHttpImplPrivate::replyDownloadData(QByteArray) + 12803 org.qt-project.QtNetwork 0x0000000109b4ead4 QNetworkReplyHttpImpl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 18284 org.qt-project.QtCore 0x0000000109e69393 QObject::event(QEvent*) + 7555 org.qt-project.QtWidgets 0x000000010686932b QApplicationPrivate::notify_helper(QObject*, QEvent*) + 2516 org.qt-project.QtWidgets 0x000000010686c648 QApplication::notify(QObject*, QEvent*) + 81367 org.bitshares.BitShares 0x00000001040ebc6e BitSharesApp::notify(QObject*, QEvent*) + 148 org.qt-project.QtCore 0x0000000109e3ea5b QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 971Now 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.
What are we to do with the "include" folder in the .dmg?
Code: [Select]git submodule update --init --recursivewill fix this
git submodule update --init --recursive
git checkout bts/0.9.0-rc1make forcebuildwebCode: [Select]The source directory /source/bitshares/libraries/fc/vendor/websocketppdoes not contain a CMakeLists.txt file.Am I missing something?
The source directory /source/bitshares/libraries/fc/vendor/websocketppdoes not contain a CMakeLists.txt file.
Where do I find that?
Quote from: onceuponatime on April 21, 2015, 07:48:15 amI'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".Can you try the "bitshares_client.exe" that is packed with the GUI executable .. it should be the CLI version and help you sync with the network
edit: let it hang logging for about 10 minutes and it eventually authed me.
this summer