Author Topic: BitShares 0.9.0-RC1 Feedback  (Read 15701 times)

0 Members and 1 Guest are viewing this topic.


Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
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???

Have you used a chain server??
http://wiki.bitshares.org/index.php/BitShares/Chain-Server
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Tuck Fheman

  • Guest
I don't want to give any more negative burns to muh friends testing, can someone tell me if this has ever been fixed?

https://bitsharestalk.org/index.php/topic,15170.msg197502.html#msg197502

Offline vikram

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.
I agree with this..

Yea, we will do an RC2 soon and hardfork will be delayed.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
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.
I agree with this..

Offline SmileyChris

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.

Offline tsaishen

  • Full Member
  • ***
  • Posts: 55
    • View Profile
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???
« Last Edit: April 22, 2015, 08:04:15 pm by tsaishen »

Offline vikram

Getting "invalid asset amount (35005)" when attempting to short bitUSD

Code: [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.

Offline vikram

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.

Xeldal

  • Guest
>Exchange>%market> When I click in the ask or buy orders columns it automatically fills the buy/sell fields which is great, however it often only fills the quantity and not the price, or fills the wrong price.

Offline youlonghun

  • Full Member
  • ***
  • Posts: 118
    • View Profile
will it adds black background then?

Offline darbon

  • Jr. Member
  • **
  • Posts: 35
    • View Profile
    • HolyTransaction
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.
wallet_approve_delegate holytransaction
https://holytransaction.com/

Offline graffenwalder

It would be nice if the buy/sell order colums listed the quantity of units. (Bitusd etc..)
The depth chart could do with it's own colum, not really usefull now.

Unable to buy/sell 35005 invalid asset ammount
« Last Edit: April 22, 2015, 06:25:59 am by graffenwalder »

lzr1900

  • Guest
suck as usual.crashing all the time

Offline lil_jay890

  • Hero Member
  • *****
  • Posts: 1197
    • View Profile
Getting "invalid asset amount (35005)" when attempting to short bitUSD

Code: [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
« Last Edit: April 22, 2015, 01:48:53 pm by lil_jay890 »