it's no trust
crash damages normal restart - solution only remove (cleaning and re-create) ~/.memorycoin (of course need constatly backup wallet.dat)

I'm find new bug:

tail -f /root/.memorycoin/debug.log
getGrantAwardsFromDatabase 640
Check Grant Awards Are Being Added for block 640
Ensure grant database up to date 640
getGrantAwardsFromDatabase 660
Check Grant Awards Are Being Added for block 660
Ensure grant database up to date 660

/var/log/syslog
bitcoind[24810]: segfault at 50 ip 0000000000488e0f sp 00007fffafbf39a0 error 4 in bitcoind[400000+2f5000]

fresh from https://github.com/memorycoin/memorycoin.git
OS:
cat /etc/issue
Ubuntu 12.04.3 LTS \n \l

ldd bitcoind
   linux-vdso.so.1 =>  (0x00007fffbeb77000)
   libboost_system.so.1.48.0 => /usr/lib/libboost_system.so.1.48.0 (0x00007f4924cb9000)
   libboost_filesystem.so.1.48.0 => /usr/lib/libboost_filesystem.so.1.48.0 (0x00007f4924a9a000)
   libboost_program_options.so.1.48.0 => /usr/lib/libboost_program_options.so.1.48.0 (0x00007f4924834000)
   libboost_thread.so.1.48.0 => /usr/lib/libboost_thread.so.1.48.0 (0x00007f4924619000)
   libdb_cxx-4.8.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-4.8.so (0x00007f492428e000)
   libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f492402f000)
   libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f4923c54000)
   libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f4923a37000)
   libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f4923736000)
   libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f492343a000)
   libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f4923224000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4922e63000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f4922c5f000)
   libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f4922a47000)
   /lib64/ld-linux-x86-64.so.2 (0x00007f4924ecb000)

P.S.
/memorycoin.conf
rpcuser=memorycoinrpc
rpcpassword=xxx
addnode=82.52.177.81:1968
addnode=209.126.73.6:1968
addnode=109.190.52.162:1968
addnode=46.16.76.217:1968

CentOS openssl package don't have EC support.
yes, i am known. i'm rebuild openssl of course (ECC enable) for CentOS.

now +1h (Ubuntu 12.04) without crash …

ok - i am try 2^N .

Ubuntu 12.04 LTS

sudo apt-get install libboost-chrono1.48-dev libboost-filesystem1.48-dev libboost-system1.48-dev libboost-program-options1.48-dev libboost-thread1.48-dev

free - 13667M
CPU E5-2620

crash in set generate mode.
./bitcoind setgenerate true 23

I am try 1.46 (by default on Ubuntu)/ 1.48 … try CentOS 6.4 … different server's - constant crash in generate mode.
 

bitcoind: db/version_set.cc:715: leveldb::VersionSet::~VersionSet(): Assertion `dummy_versions_.next_ == &dummy_versions_'

Temporary "solution"

1. Copy ~/.memorycoin/wallet.dat to safe place
2. Goto win laptop/desktop and install http://www.memorycoin.org/downloads/memorycoin.zip (memorycoin-qt for win)
3. Run memorycoin-qt (win) and wait "normal" run
4. Shutdown/exit memorycoin-qt (win)
5. Copy wallet.dat (from linux server) to win via ssh/ftp/etc
6. Move wallet.dat to C:\Users\%Username%\AppData\Roaming\MemoryCoin
7. Run memorycoin-qt (win) and wait
9. See their coins
10. cp ~/.memorycoin/memorycoin.conf /tmp
11. rm -rf ~/.memorycoin/ (!!! it's delete old setup)
12. ./bitcoind
13. cp /tmp/memorycoin.conf ~/.memorycoin/memorycoin.conf
14. ./bitcoind --daemon
15. Sent money from win to new linux account (optional)
16. Profit !

MJfgAqnNZXH84akVpViv6rFyAXRQKqkg4h

Linux crash similar +1

 ./bitcoind getinfo
{
    "version" : 85200,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 2.69230769,
    "blocks" : 240,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 0.00000097,
    "testnet" : false,
    "keypoololdest" : 1387117140,
    "keypoolsize" : 102,
    "paytxfee" : 0.00000000,
    "errors" : ""
}

after small time
./bitcoind getinfo
error: {"code":-1,"message":"CDB() : can't open database file wallet.dat, error -30974"}

...

[/quote]

Okay - it would be helpful to have the debug.log following the crash - memorycoincc@gmail.com

[/quote]

I'm sent email too.

./bitcoind : Error loading block database.
Do you want to rebuild the block database now?
bitcoind: db/version_set.cc:715: leveldb::VersionSet::~VersionSet(): Assertion `dummy_versions_.next_ == &dummy_versions_' failed.

: Error loading block database.
Do you want to rebuild the block database now?
bitcoind: db/version_set.cc:715: leveldb::VersionSet::~VersionSet(): Assertion `dummy_versions_.next_ == &dummy_versions_' failed.

hmm … solution?

http://www.btc38.com/trade.html?btc38_trade_coin_name=pts
This is a consequence of the emergence of new coins? I'm disappointed.

Again:
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::thread_resource_error> >'
  what():  boost::thread_resource_error

I do not understand why the creators of the coins were in a hurry? Someone was chasing them?
Why not debug, debug and next debug and release a worked/tested solution (without so many bugs) - We ourselves undermine PTS.

ver. of lib boost?

my boost 1.46 from Ubuntu repository.

Compiled from https://github.com/memorycoin/memorycoin.git (Ubuntu 12.04 & CentOS 6.4)

periodically crash with the message:
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::thread_resource_error> >'
  what():  boost::thread_resource_error: Resource temporarily unavailable

Different server, different size of RAM (16, 32, 64G).

What could be the reason?