Date: 12/31/2013 00:53
To: MMTkW4RDPqY63D6B9rLXWBQe8KdXKAZf8P
Debit: -20.00 MMC
Transaction fee: -0.0001 MMC
Net amount: -20.0001 MMC
Transaction ID: a67f39bb124c36183211d4ebe5441dfb53df78b25c515b892093a546dafbe227

Congratulation pinwc4, you were the first one who got my reward . I payout for you already.
Thank you

Received and appreciated.  It was quite good luck for me, I had just pointed some workers to your pool about 5 minutes before the block was discovered. 

Bonus is paid out of my own pocket.

Bonus received.  Your generosity is appreciated.

Thanks

Hopefully with all that hash we will see a block soon.  Should average about a block an hour based on the coin calculator.  Is that correct?

Anyone tried the Mac version yet, when I get home I will try it and add a few more clients to the pool. 

Last week I was mining this coin with no problem, well outside of the Linux crashes.  This week the daemon no longer crashed but I do not seem to be getting any coins at all. 

When looking through the logs the only thing that stands out is an entry like this:
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
I do not know if that is related to my problem but it looks like a bad thing.

My friend is experiencing the same behavior.  Between us we have 55 systems running, mostly HP or similar servers.  Based on the calculator we should be seeing a block of coins approximately every few hours.  However we have gotten only 2 and they only showed up after some restarts.  Running this for a long time never adds to the balance of the wallet.dat that is shared across the servers.

We are running ubuntu 13.10, though I guess we could rebuild if necessary, I think he pxe boots his servers so it would be quick for him not as quick for me. 

I compiled the source using the following steps:
sudo su
apt-get install -y build-essential m4 libssl-dev libdb++-dev libboost-all-dev libminiupnpc-dev git
cd
rm -rf gmp-5.1.3.tar.bz2 gmp-5.1.3
wget http://mirrors.kernel.org/gnu/gmp/gmp-5.1.3.tar.bz2
tar xjvf gmp-5.1.3.tar.bz2
cd gmp-5.1.3
./configure --enable-cxx
make -j8
make install
cd
git clone https://github.com/memorycoin/memorycoin
cd memorycoin/src
cp makefile.unix makefile.my
sed -i -e 's/$(OPENSSL_INCLUDE_PATH))/$(OPENSSL_INCLUDE_PATH) \/usr\/local\/include)/' makefile.my
sed -i -e 's/$(OPENSSL_LIB_PATH))/$(OPENSSL_LIB_PATH) \/usr\/local\/lib)/' makefile.my
sed -i -e 's/$(LDHARDENING) $(LDFLAGS)/$(LDHARDENING) -Wl,-rpath,\/usr\/local\/lib $(LDFLAGS)/' makefile.my
make -f makefile.my -j8
strip bitcoind
mv bitcoind ~/memorycoind
cd
mkdir -p .memorycoin
cd .memorycoin

I then put in a copy of a basic memorycoin.conf file:

rpcuser=pinwc4
rpcpassword=x
rpcport=1925
rpcallow=*
server=1
genproclimit=-1
gen=1
addnode=81.17.19.139
Then finally I place a copy of all the other .memorycoin folder files in the directory.  This includes everything so I do not have to resync, and also so I am sharing a wallet.dat file across the machines. 

This process worked fine last week however this week it has not been resulting in any mining.  The CPU usage is high, memory usage is high, I see a HPM figure that looks good on each system, but no coins are found. 

If anyone has any insight I would appreciate it.  This has baffled me for a bit.  With the holidays I have not been able to spend time troubleshooting it but I figure I must be doing something stupid.

I am interested in acquiring some PTS.  Unless you are willing to send first I would prefer to go through escrow.  If someone is willing to trade more PTS I would like to get more than 10, just was hoping to be able to get at least 10. 

Awesome, it has definitely helped me tremendously.  I have not compiled your latest source that has other changes, I am still just running my modified copy.

But with those 2 simple changes I have been running for over 3 hours at this point with no memory increase beyond what happens in the first few minutes.  I pushed this out to my other machines and they are happy as well. 

Now I just wish it would find another block so I am confident it is working but that is a rare thing to encounter in such a short time. 

In digging a little further into this I have found I can stop the memory leak, though I do not know if what I did prevents true mining as I have not discovered a block since my testing of the change. 

In momentum.cpp around line 200 where the line "return results;" is I added 2 lines prior.

delete aesThreads;
delete sha512Threads;

I now have no memory leak, but wonder if I am still hashing properly.  I would think these lines are not necessary as boost should clean up but doing the above keeps my memory usage stable.  I am showing a good hash/min and CPU usage is high so it is doing something.

Since it looks like the code assumes the threads have completed by that point I think this is a safe operation.  However I am not a programmer so I am really just guessing.