x64 wallet doesnt start instead shows an error message, please fix.

x86 wallet working fine!

coolspeed
delegate.coolspeed
dac.coolspeed

updated to 0.4.12.  Version published.

yes,i am also aware of this,the RAM usage drop down after  server restart.

Quote from: wackou on September 05, 2014, 09:08:46 AM

Quote from: crazybit on September 05, 2014, 01:00:28 AM
btw, the 0.4.12 version consumes too much RAM. about 1.5G

yeah, I initially thought that too, but then I checked and a good part of it was due to the reindexing, which is either leaking a bit or doesn't return the memory to the system immediately (this is an OS thing, the client can't do anything about it I believe). However, this only happens the first time you run the client when it needs to upgrade the db.
Shutting down the client and relaunching it "solved" it for me.

Quote from: crazybit on September 05, 2014, 01:00:28 AM
btw, the 0.4.12 version consumes too much RAM. about 1.5G

yeah, I initially thought that too, but then I checked and a good part of it was due to the reindexing, which is either leaking a bit or doesn't return the memory to the system immediately (this is an OS thing, the client can't do anything about it I believe). However, this only happens the first time you run the client when it needs to upgrade the db.
Shutting down the client and relaunching it "solved" it for me.

Quote from: bytemaster on September 04, 2014, 09:38:37 PM

Quote from: xeroc on September 04, 2014, 09:30:05 PM
I am getting more and more used to theses updates for the delegates ... second time in a row I havent missed a single block during update .. yeehha :)

Now that stability has been mostly addressed, we are going to aim for weekly sprints with new features and bug fixes.   We will also be making some "donations" to the delegates to compensate them for the added work they are doing by updating on such a frequent basis.

Emski just made me aware that I skrewed up again .. not missing a block but somehow managed to have both wallets unlocked for a longer time producing forks .. this enerves me a lot as I wrote scripts to prevent all of this
https://github.com/xeroc/pytshares/blob/master/enable-main.py
https://github.com/xeroc/pytshares/blob/master/enable-backup.py
I have no f**** clue how I skrewed it up this time ...

In a quick discussion with emski .. I desiced to shutdown the backup delegate completely and run only one delegate machine .. when doing updates I will probably miss some blocks .. but as we know .. missing blocks is not as bad as forks .. sorry for the invonvinience .. I learned my lesson

Quote from: xeroc on September 05, 2014, 06:40:48 AM
Nice .. I found some fixes too from 2012 :)
Good to know i dont need to downgrade gcc ..
thx

Yeah, I just wonder when it'll make it into stable release...

sun.delegate.service
moon.delegate.service
@ v0.4.12
and public data update
{"version","0.4.12"}

Nice .. I found some fixes too from 2012 :)
Good to know i dont need to downgrade gcc ..
thx

Quote from: bytemaster on September 04, 2014, 09:51:18 PM

Quote from: xeroc on September 04, 2014, 09:49:19 PM

Quote from: bytemaster on September 04, 2014, 09:43:54 PM

Quote from: xeroc on September 04, 2014, 09:38:39 PM
Hu ... on ArchLinux I am getting this internal compiler error:

Code Select Expand


/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp: In member function 'void bts::blockchain::cha
in_database::open(const fc::path&, fc::optional<fc::path>, std::function<void(float)>)':
/home/delegate/bitsharesx/libraries/blockchain/chain_database.cpp:1145:63: internal compiler error: in calc_dfs_
tree, at dominance.c:401
    } FC_RETHROW_EXCEPTIONS( warn, "", ("data_dir",data_dir) ) }
                                                               ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
libraries/blockchain/CMakeFiles/bts_blockchain.dir/build.make:570: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o' failed
make[2]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o] Error 1
CMakeFiles/Makefile2:847: recipe for target 'libraries/blockchain/CMakeFiles/bts_blockchain.dir/all' failed
make[1]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/all] Error 2
Makefile:76: recipe for target 'all' failed
make: *** [all] Error 2


Upgrade GCC and make sure you have plenty of ram.

gcc 4.9.1 ... 6 GB RAM .. seems to be a distribution-related issue :(

Downgrade GCC... 4.8 seems to work.  4.9 seems like it may be too new/buggy.

Just to say I confirm this bug as well. Running the latest Arch too.

EDIT: Pretty sure that there is a fix for this, just waiting upstream somewhere: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62079

Delegates:
www.minebitshares-com
www2.minebitshares-com

and seed nodes:
euseednode.minebitshares.com  54.77.51.177
auseednode.minebitshares.com  54.79.27.224

Updated to 0.4.12

The % progress display when re-indexing the database on startup is very useful...

btsx_feed_auto.py price feed scripts is also updated

*.chinese @ v0.4.12

Quote from: bytemaster on September 04, 2014, 07:03:47 PM
https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.12

Delegates & Seed Nodes should upgrade ASAP. 
Publish your version info as "0.4.12" after you upgrade to keep my vote.

I think we need checksum of every release,  that we can make sure our download is correct.

delegate.taolje
updated 0.4.12 and the automatic feed price scripts.
Good job, +5% +5% +5%

I have win7x32, I downloaded the exe 0.4.12 in bitshare-x.info and it won't open the installation file, I think the exe file is winx64 because size is 33mb. I checked the github releases and downloaded the x32 there.

There should be x64 and x32 download files in bitshare-x.info

Quote from: alt on September 05, 2014, 02:13:29 AM
I suggest  delegate  to update the automatic feed price scripts.
the main different is use the median price to replace the average price.
you can change the pararm "median_length" to adjust the price change latency.
because version 0.4.12 will use feed price to decide  the min cover price,
we need to protect the cover order from a serial margin call,
maybe cause of a suddenly price drop with a short period at the central trade site.
my English is poor, maybe not say it clearly   ???

Quote from: alt on September 05, 2014, 02:06:35 AM
updated:
1. update config file
2. use median price to replace average price, to protect system from  a suddenly drop price with a short period at the central trade site.