Experimental pre-0.8 builds for testing

[niko]

^^^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?

[1714233744]

1714233744

[1714233744]

1714233744

[1714233744]

1714233744

[1714233744]

1714233744

[dserrano5]

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?

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.

[notme]

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?

bad_alloc.... do you have no swap?

[rasputin]

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.

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

Monit starts bitcoind whenever it isn't running, and forces a restart once the process is using more than 420MB of physical memory.

[BkkCoins]

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.

[dserrano5]

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

[BkkCoins]

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

I get these numbers: 39 66 1000 1020
But it's running fine atm, and steady at 660 MB total.

[nexusakachus]

runs smooooooth



macbook pro 6.2 osx 10.8.3 build 12D58

[notme]

Any word on when this will be released?

[Diapolo]

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

[notme]

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://bitcointalk.org/index.php?topic=142151.0

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.

[notme]

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://bitcointalk.org/index.php?topic=142151.0

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://bitcointalk.org/index.php?topic=145184.msg1540252#msg1540252

[Pieter Wuille]

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!