4096
General Discussion / Re: BitShares 0.9.0 Feedback
« on: April 24, 2015, 06:00:41 am »why did you remove the tray icon?Better if there is a confirmation before quit.
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.
4097
General Discussion / Re: BitShares 0.9.0-RC2 Feedback
« on: April 24, 2015, 05:59:24 am »After resyncing the chain, client is using ~2 GB memory. After entering password to log in, client slowly builds memory usage to just over 5GB until wallet opens and it drops to around 4.5 GB and stays there. After clicking on a market in the >Exchange> tab the client crashes. It only crashes the first time I do this after a new resync while memory usage is over 4.5 GB. If I restart the client, memory usage is down to around 1.5 GB and it never crashes again when clicking on a market from the Exchange tab.Possible memory leak while upgrading 'wallet' (not the chain replay).
I met similar issue with v0.9.0-rc1: https://bitsharestalk.org/index.php/topic,15851.msg203714.html#msg203714
4098
General Discussion / Re: BitShares 0.9.0 Feedback
« on: April 24, 2015, 05:53:28 am »Having troubles building 0.9.0git submodule update --init --recursiveCode: [Select]cmake .
...
CMake Error at libraries/fc/CMakeLists.txt:193 (add_subdirectory):
The source directory
/home/local/bitshares/libraries/fc/vendor/websocketpp
does not contain a CMakeLists.txt file.
4099
General Discussion / Re: BitShares 0.9.0-RC2 Feedback
« on: April 23, 2015, 07:06:44 am »Is unusual to see your open orders in your order history list.The order list in the GUI is really strange. It doesn't contain shorts in an older release.
My perception on Order History list are already completed trades, there is Open Order List anyway I would suggest to remove it in the Order History.
4100
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 21, 2015, 11:48:34 pm »
Possible memory leak while 'Repairing key record'.
I was running the client with a max_memory limit, it crashed:
I was running the client with a max_memory limit, it crashed:
Code: [Select]
Continuing wallet upgrade...
Repairing key record 11746MEM CPU 555.43 MEM 4814328 MAXMEM 4814328 STALE 1721
4101
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 21, 2015, 11:15:41 pm »Your issue is probably caused by the poor performance while fetching historical (matched) market orders especially in non-BTS market. See https://github.com/BitShares/bitshares/issues/1202.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.
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.
And perhaps there are race conditions somewhere...
4102
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 21, 2015, 09:42:44 pm »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.Maybe this is caused by the API change "all numbers should be passed in as strings" as well.
@svk31
4103
General Discussion / Re: look at this new order book
« on: April 21, 2015, 09:40:11 pm »I have change push service to port 80It's will be better if use wss:// on port 443.it's weired...
What port are you using for the socket? Unless it's 80, or 443, most shared access networks will block it (public places, work, etc)
You're right, it's on port 8080, guess that's why.
4104
General Discussion / Re: look at this new order book
« on: April 21, 2015, 08:59:28 pm »Old web proxies may have issues with web sockets. Is there a (maybe transparent) proxy in your working network?I have change push service to port 80it's weired...
What port are you using for the socket? Unless it's 80, or 443, most shared access networks will block it (public places, work, etc)
You're right, it's on port 8080, guess that's why.
It still doesn't work for me from my work computer, but I checked on my phone and there it's fine.
4105
中文 (Chinese) / Re: 哪位兄弟送一个BTS注册网络钱包吧！
« on: April 21, 2015, 08:51:34 pm »
BTS国内注册的水龙，菜鸟弄的。http://www.btaer.com/
4106
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 21, 2015, 08:38:11 pm »The 0 numbers issue could caused by the API change "all numbers return as strings"Overall slick! Here's what I found in the GUI on OSX:
Exchange page
- MPA and UIA tables are not populated
Market 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 behavior
Suggestions 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.
4107
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 21, 2015, 08:35:16 pm »No way to do titan anymore?TITAN is possible with CLI/console.
4108
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 21, 2015, 08:31:06 pm »
It took me 4 hours to re-index on my non-SSD machine with --statistics-enabled, and 8770 seconds with no --statistics-enabled. Heavy IO operations.
4109
General Discussion / Re: BitShares 0.9.0-RC1 Feedback
« on: April 21, 2015, 05:52:58 am »edit: let it hang logging for about 10 minutes and it eventually authed me.Looks like it's re-scaning the wallet (for transactions).
4110
