Since 0.8.0 final is released, I'd like to thank everyone who participated in testing the pre-release versions. Several problems were found after user reports, and others at least showed that many people noticed the improvements. There is certainly still room for improvement, but we're making progress in small (and sometimes bigger) steps.
Thanks!
Topic: Experimental pre-0.8 builds for testing (Read 19808 times)
Any word on when this will be released?
I'm sure we will see an RC2 and perhaps an RC3 before this version gets released.
Dia
Actually, this wasn't even RC1.
RC1 is out now though:
https://bitcointalksearch.org/topic/bitcoin-qt-bitcoind-version-080-release-candidate-1-142151
Not many complaints, solid for me too. Hopefully we can get enough testing and get this pushed out before too long. It really is a huge improvement.
0.8.0 is out: https://bitcointalksearch.org/topic/m.1540252
Any word on when this will be released?
I'm sure we will see an RC2 and perhaps an RC3 before this version gets released.
Dia
Actually, this wasn't even RC1.
RC1 is out now though:
https://bitcointalksearch.org/topic/bitcoin-qt-bitcoind-version-080-release-candidate-1-142151
Not many complaints, solid for me too. Hopefully we can get enough testing and get this pushed out before too long. It really is a huge improvement.
Any word on when this will be released?
I'm sure we will see an RC2 and perhaps an RC3 before this version gets released.
Dia
Any word on when this will be released?
runs smooooooth
macbook pro 6.2 osx 10.8.3 build 12D58
macbook pro 6.2 osx 10.8.3 build 12D58
There probably is a threads/process limit set by the virtual host. I don't know how to check that off hand but I recall there being some vz cmds and beancounter type stuff I could find out and check.
Code:
# grep numproc /proc/user_beancounters
But it's running fine atm, and steady at 660 MB total.
There probably is a threads/process limit set by the virtual host. I don't know how to check that off hand but I recall there being some vz cmds and beancounter type stuff I could find out and check.
Code:
# grep numproc /proc/user_beancounters
Thank you for the multiple suggestions. I haven't had time to explore it more fully yet. It is running on a 1GB VPS under OpenVZ. I believe this has no swap or at least is handled differently. At this moment it's using 686 MB / 1024MB available, and this is typical. This includes electrum and bitcoind. About 468 MB of that is bitcoind. I think it does increase over time but haven't kept records.
There probably is a threads/process limit set by the virtual host. I don't know how to check that off hand but I recall there being some vz cmds and beancounter type stuff I could find out and check.
I could probably fix it by just restarting bitcoind and electrum every 24 hours. But for now I'll let it go and check now and then to see if the memory use climbs up.
There probably is a threads/process limit set by the virtual host. I don't know how to check that off hand but I recall there being some vz cmds and beancounter type stuff I could find out and check.
I could probably fix it by just restarting bitcoind and electrum every 24 hours. But for now I'll let it go and check now and then to see if the memory use climbs up.
I keep getting crashes on my bitcoind install running an Electrum server.
*snip*
This seems to happen every few days for me right now. Is there a memory leak that is causing eventual depletion?
Absolutely, at least for me (64-bit Linux). The memory leak predates the 0.8 build, just for the record.*snip*
This seems to happen every few days for me right now. Is there a memory leak that is causing eventual depletion?
I've worked around it by installing monit and creating this config file:
Code:
$ cat /etc/monit/conf.d/bitcoind
check process bitcoin matching "bitcoind .*daemon"
start program "/home/bitcoin/bin/bitcoind -datadir=/home/bitcoin/.bitcoin -daemon"
as uid bitcoin and gid nogroup
stop program "/home/bitcoin/bin/bitcoind -datadir=/home/bitcoin/.bitcoin stop"
as uid bitcoin and gid nogroup
if mem > 420 MB for 3 cycles then restart
if 3 restarts within 10 cycles then timeout
check process bitcoin matching "bitcoind .*daemon"
start program "/home/bitcoin/bin/bitcoind -datadir=/home/bitcoin/.bitcoin -daemon"
as uid bitcoin and gid nogroup
stop program "/home/bitcoin/bin/bitcoind -datadir=/home/bitcoin/.bitcoin stop"
as uid bitcoin and gid nogroup
if mem > 420 MB for 3 cycles then restart
if 3 restarts within 10 cycles then timeout
Monit starts bitcoind whenever it isn't running, and forces a restart once the process is using more than 420MB of physical memory.
Dude, memory is way too cheap to put yourself through the torture of running a machine with 1 GB of ram.
Unless you're paying for a server such as a VPS. In this case every MB of memory pushes the monthly cost up.
I keep getting crashes on my bitcoind install running an Electrum server.
From the debug log:
Code:
02/03/13 02:35:30 CTxMemPool::accept() : accepted a3fbde782d (poolsz 713)
02/03/13 02:35:31
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
bitcoin in ThreadMessageHandler()
02/03/13 02:35:31
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
bitcoin in ThreadMessageHandler()
This seems to happen every few days for me right now. Is there a memory leak that is causing eventual depletion?
bad_alloc.... do you have no swap?
Dude, memory is way too cheap to put yourself through the torture of running a machine with 1 GB of ram.
Unless you're paying for a server such as a VPS. In this case every MB of memory pushes the monthly cost up.
I keep getting crashes on my bitcoind install running an Electrum server.
From the debug log:
Code:
02/03/13 02:35:30 CTxMemPool::accept() : accepted a3fbde782d (poolsz 713)
02/03/13 02:35:31
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
bitcoin in ThreadMessageHandler()
02/03/13 02:35:31
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
bitcoin in ThreadMessageHandler()
This seems to happen every few days for me right now. Is there a memory leak that is causing eventual depletion?
My "memory" problems in my VPS turned out to be not related to the available RAM, but to the number of running processes/threads (I have a limit of 128 threads). You may be finding the same issue.
^^^I've installed and verified pre-0.8 from scratch several times on a 768 MB fossil running WinXP (see earlier posts). Never got close to running out of RAM. IIRC peak usage was 190 MB. Might be a problem specific to Linux?
Dude, memory is way too cheap to put yourself through the torture of running a machine with 1 GB of ram.
Unless you're paying for a server such as a VPS. In this case every MB of memory pushes the monthly cost up.
I keep getting crashes on my bitcoind install running an Electrum server.
From the debug log:
Code:
02/03/13 02:35:30 CTxMemPool::accept() : accepted a3fbde782d (poolsz 713)
02/03/13 02:35:31
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
bitcoin in ThreadMessageHandler()
This seems to happen every few days for me right now. Is there a memory leak that is causing eventual depletion?
Tested bitcoin-0.7.1-353-g3afefd8-linux from scratch on a low-spec Ubuntu 12.04 w/ 0,9GHz Celeron M CPU & 1GB ram on ext4 on external USB2.0 HDD.
It took me 2 computer resets, because bitcoin-qt would gobble up all RAM bringing the machine to a non-responsive state.
Approximately 48 hours is what I needed to finish syncing from scratch. CPU was loaded @ 60% throughout.
I always had 8-9 connections on a fast internet link.
Datadir weighed in at 6,2 GB.
The bright side is that bitcoin-qt now shuts down in 3 secs. (the GUI still takes 2+ mins to show up when launching bitcoin-qt)
It took me 2 computer resets, because bitcoin-qt would gobble up all RAM bringing the machine to a non-responsive state.
Approximately 48 hours is what I needed to finish syncing from scratch. CPU was loaded @ 60% throughout.
I always had 8-9 connections on a fast internet link.
Datadir weighed in at 6,2 GB.
The bright side is that bitcoin-qt now shuts down in 3 secs. (the GUI still takes 2+ mins to show up when launching bitcoin-qt)
Dude, memory is way too cheap to put yourself through the torture of running a machine with 1 GB of ram.
Tested bitcoin-0.7.1-353-g3afefd8-linux from scratch on a low-spec Ubuntu 12.04 w/ 0,9GHz Celeron M CPU & 1GB ram on ext4 on external USB2.0 HDD.
It took me 2 computer resets, because bitcoin-qt would gobble up all RAM bringing the machine to a non-responsive state.
Approximately 48 hours is what I needed to finish syncing from scratch. CPU was loaded @ 60% throughout.
I always had 8-9 connections on a fast internet link.
Datadir weighed in at 6,2 GB.
The bright side is that bitcoin-qt now shuts down in 3 secs. (the GUI still takes 2+ mins to show up when launching bitcoin-qt)
It took me 2 computer resets, because bitcoin-qt would gobble up all RAM bringing the machine to a non-responsive state.
Approximately 48 hours is what I needed to finish syncing from scratch. CPU was loaded @ 60% throughout.
I always had 8-9 connections on a fast internet link.
Datadir weighed in at 6,2 GB.
The bright side is that bitcoin-qt now shuts down in 3 secs. (the GUI still takes 2+ mins to show up when launching bitcoin-qt)
Obviously, the new code offers a great improvement in the speed of initial verification. New users can now set up a full node and start using it much faster then opening and verifying a PayPal account. Great.
I have to ask now - excuse my ignorance - what is the worst thing that could happen if there is a mistake or an oversight in the new algorithm? Obviously, block hashes are identical to those from the current reference client. Does this mean all unspent coins are safe and secure? Is there any serious risk in moving forward with 0.8?
I have to ask now - excuse my ignorance - what is the worst thing that could happen if there is a mistake or an oversight in the new algorithm? Obviously, block hashes are identical to those from the current reference client. Does this mean all unspent coins are safe and secure? Is there any serious risk in moving forward with 0.8?
Great results with bitcoin-0.7.1-353-g3afefd8-win32
bootstrap.dat was in place. I didn't see much multithreading, but the blockchain bootstrap and update ran fast. debug.log excerpts:
Worked fine with a small transaction in and back out.
- Windows 7
- HP 8440 laptop with 4 cores
- 8GB RAM
- FiOS connection
- bitcoin-qt.exe -datadir=C:\Users\username\AppData\Local\LargeDB\Bitcoin071 -logtimestamps -dbcache=250
bootstrap.dat was in place. I didn't see much multithreading, but the blockchain bootstrap and update ran fast. debug.log excerpts:
Code:
2013-01-23 03:11:54 SetBestChain: new best=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 height=1 work=8590065666 tx=2 date=2009-01-09 02:54:252013-01-23 03:44:50
Loaded 193000 blocks from external file in 1976602ms
2013-01-23 03:59:43 SetBestChain: new best=00000000000006a1e50bedf15148d15aafa469aa02c0e9ad1d8fa3a479bb770e height=193001 work=420251477813705134572 tx=5770265 date=2012-08-09 06:17:15
2013-01-23 04:05:29 SetBestChain: new best=000000000000046242d4984ecf2217e9afa113f2835bffbff118f2df4d80b216 height=194000 work=429298255956894417423 tx=5993959 date=2012-08-15 10:02:59
2013-01-23 04:44:27 SetBestChain: new best=000000000000034a7dedef4a161fa058a2d67a173a90155f3a2fe6fc132e0ebf height=200000 work=493482865315456673820 tx=7316696 date=2012-09-22 10:45:59
2013-01-23 05:48:37 SetBestChain: new best=000000000000048b95347e83192f69cf0366076336c639f9b7228e9ba171342e height=210000 work=628963747775700992096 tx=9344662 date=2012-11-28 15:24:38
2013-01-23 06:52:09 SetBestChain: new best=000000000000036d1e5c410c393017277f8ccb59cb30a9143e818e788ecd2515 height=217000 work=726735151411243146775 tx=11340810 date=2013-01-18 09:24:24
2013-01-23 06:58:57 SetBestChain: new best=0000000000000369ae94ccf9ac51e1b89251ba18904c1d0685f31c100d0eab59 height=217650 work=735807150813835318925 tx=11562582 date=2013-01-23 04:29:53
2013-01-23 07:00:31 SetBestChain: new best=000000000000049506cb15e13a38c2f9116d530603698d0bf3dabcb0a3bf091a height=217665 work=736016504646202830590 tx=11569307 date=2013-01-23 06:59:32
Worked fine with a small transaction in and back out.
downloaded bitcoin-0.7.1-353-g3afefd8-win32-setup
win 7, 64 bit
i7
8 gb ram
laptop
uninstalled version 0.7.2. the last one from bitcoin.org
I did not delete folder or any files from where older version was
installed this bitcoin-0.7.1-353-g3afefd8-win32-setup
it sees my wallet as encrypted and locked (like it should be)
started at
15:43
ventilator is not silent, but moderate, with ocasional overdrives that last 5 to 10 seconds
the message says "reindexing blocks on disk"
it never went over 8 active connections,
I connect to internet through nearby hotspot,
map port using upnp is checked by default,
connect through socks proxy was unchecked by default
i did not touch that at all
I don't know how to portforward bitcoin and never did that, but I noticed the green bar on the last released
version 0.7.2, and it oscilated between 19 and 36 connections the other day when I looked
15:53 --> 168000 blocks
16:03 --> 193500 blocks
16:13 --> 209300 blocks
ventilator started spinning loudly non-stop
after 200k blocks
16:23 --> 213000 blocks
blockchain was last updated on my disk with version 0.7.2 , a few days ago, so last 300 will be updated with this
new version,
16:33 --> 216200 blocks
ventilator did not slow down from block 200k
16:37 --> 500 blocks remaining
16:38 --> 239 blocks remaining, message changed to "synchronizing with network"
ventilator slowed down significantly, almost silent, ocasional overdrives of few seconds
16:41 --> 95 blocks remaining
16:43 --> 10 blocks remaining
looks like it is ok
I shut it down with end process tree
after 15 sec i started it again
it took about 30-35 seconds to open gui
connected to someone within 5 seconds.
I dont like the idea of sending coins into it.
armory 0.87
16:47 started scanning blockchain
16:50 armory shows the same number of blocks as bitcoin gui...
-------------------------------------------------------------------------------------------
bitcoin was turned off for at least half an hour before restart,
after computer restart,
I manually started bitcoin (option to start with windows is turned off)
it got stuck at "verifying block database integrity"
and after a few minutes error message prompted on screen
"corupted block database detected please restart the client with -reindex"
how to even do that ?
I guess I will delete all from bitcoin folder and start actual full blockchain download
-------------------------------------------------------------------------------------------
laptop was turned off
after start, bitcoin opened with no problems
------------------------------------------------------------------------------------------
today I deleted all files from bitcoin folder,
started download
after 15 minutes it processed 102k blocks
after 30 min 120k blocks
after 1 hour 133k
90 min 139k
2 and half hours 155k
4 hours 185k
6 hours 206k
7 hours 214k
finished exactly after 8 hours
I started armory 0.87 offline icon from start menue while bitcoin still had 350 blocks to verify
I pressed a button in armory to go online,
it started scanning the blockchain, finished showed current block count, and it said it is connected,
but watching wallets had balances -- btc and I was not able to create unsigned transactions
I don't know if this is armory or bitcoin problem
after I turned armory off, and started the regular icon of armory (not the one with word offline in name)
armory scanned and connected and balances were in place, and I was able to create unsigned transactions
---------------------------------------------------------------------------------------------------------------
today again bitcoin "stopped responding" on startup,
nothing unusual was done yesterday, or forced shutdown, or settings changed
but, after a minute it did actually start, connected, loadaded blocks
-----------------------------------------------------------------------------------------------
win 7, 64 bit
i7
8 gb ram
laptop
uninstalled version 0.7.2. the last one from bitcoin.org
I did not delete folder or any files from where older version was
installed this bitcoin-0.7.1-353-g3afefd8-win32-setup
it sees my wallet as encrypted and locked (like it should be)
started at
15:43
ventilator is not silent, but moderate, with ocasional overdrives that last 5 to 10 seconds
the message says "reindexing blocks on disk"
it never went over 8 active connections,
I connect to internet through nearby hotspot,
map port using upnp is checked by default,
connect through socks proxy was unchecked by default
i did not touch that at all
I don't know how to portforward bitcoin and never did that, but I noticed the green bar on the last released
version 0.7.2, and it oscilated between 19 and 36 connections the other day when I looked
15:53 --> 168000 blocks
16:03 --> 193500 blocks
16:13 --> 209300 blocks
ventilator started spinning loudly non-stop
after 200k blocks
16:23 --> 213000 blocks
blockchain was last updated on my disk with version 0.7.2 , a few days ago, so last 300 will be updated with this
new version,
16:33 --> 216200 blocks
ventilator did not slow down from block 200k
16:37 --> 500 blocks remaining
16:38 --> 239 blocks remaining, message changed to "synchronizing with network"
ventilator slowed down significantly, almost silent, ocasional overdrives of few seconds
16:41 --> 95 blocks remaining
16:43 --> 10 blocks remaining
looks like it is ok
I shut it down with end process tree
after 15 sec i started it again
it took about 30-35 seconds to open gui
connected to someone within 5 seconds.
I dont like the idea of sending coins into it.
armory 0.87
16:47 started scanning blockchain
16:50 armory shows the same number of blocks as bitcoin gui...
-------------------------------------------------------------------------------------------
bitcoin was turned off for at least half an hour before restart,
after computer restart,
I manually started bitcoin (option to start with windows is turned off)
it got stuck at "verifying block database integrity"
and after a few minutes error message prompted on screen
"corupted block database detected please restart the client with -reindex"
how to even do that ?
I guess I will delete all from bitcoin folder and start actual full blockchain download
-------------------------------------------------------------------------------------------
laptop was turned off
after start, bitcoin opened with no problems
------------------------------------------------------------------------------------------
today I deleted all files from bitcoin folder,
started download
after 15 minutes it processed 102k blocks
after 30 min 120k blocks
after 1 hour 133k
90 min 139k
2 and half hours 155k
4 hours 185k
6 hours 206k
7 hours 214k
finished exactly after 8 hours
I started armory 0.87 offline icon from start menue while bitcoin still had 350 blocks to verify
I pressed a button in armory to go online,
it started scanning the blockchain, finished showed current block count, and it said it is connected,
but watching wallets had balances -- btc and I was not able to create unsigned transactions
I don't know if this is armory or bitcoin problem
after I turned armory off, and started the regular icon of armory (not the one with word offline in name)
armory scanned and connected and balances were in place, and I was able to create unsigned transactions
---------------------------------------------------------------------------------------------------------------
today again bitcoin "stopped responding" on startup,
nothing unusual was done yesterday, or forced shutdown, or settings changed
but, after a minute it did actually start, connected, loadaded blocks
-----------------------------------------------------------------------------------------------
Running 2 nodes, everything seems to work and downloading is definitely faster
Jump to: