so i gave the new version a try as the previous always blocked when i unlocked for minting.
the same is happening again...
after unlocking, i see this
ThreadRPCServer method=walletpassphrase
uint256HashMap:Set(517/1024) data=56 sz=57344
uint256HashMap:Set(2557/4096) data=56 sz=229376
uint256HashMap:Set(5117/8192) data=64 sz=524288
askfor tx 8bffe1d321592b6218fd 0
sending getdata: tx 8bffe1d321592b6218fd
askfor tx 8bffe1d321592b6218fd 1452006623000000
CTxMemPool::accept, fCheckInputs = 1, fOnlyCheckWithoutAdding = 0
addUnchecked(): size 0
CTxMemPool::accept() : accepted 8bffe1d321
received getdata for: tx 8bffe1d321592b6218fd
uint256HashMap:Set(10237/16384) data=56 sz=917504
uint256HashMap:Set(20477/32768) data=64 sz=2097152
uint256HashMap:Set(40957/65536) data=56 sz=3670016
ThreadRPCServer method=getinfo
uint256HashMap:Set(81917/131072) data=64 sz=8388608
ThreadRPCServer method=getinfo
keypool added key 105, size=101
2016-01-05 15:12:53 UTC Flushing wallet.dat
Flushed wallet.dat 5ms
ThreadRPCServer method=getinfo
uint256HashMap:Set(163837/262144) data=56 sz=14680064
uint256HashMap:Set(327677/524288) data=64 sz=33554432
ThreadRPCServer method=getinfo
ThreadRPCServer method=listtransactions
ThreadRPCServer method=getinfo
socket recv error 110
disconnecting node 58.9.152.88:6661
trying connection 87.251.188.194:6661 lastseen=-2.4hrs
connected 87.251.188.194:6661
Added time data, samples 10, offset -1 (+0 minutes)
Moving 87.251.188.194:6661 to tried
version message: version 60005, blocks=142900
accepted alert 7, AppliesToMe()=0
Added 255 addresses from 87.251.188.194: 16 tried, 8198 new
Added 263 addresses from 87.251.188.194: 16 tried, 8271 new
uint256HashMap:Set(655357/1048576) data=56 sz=58720256
ThreadRPCServer method=getinfo
over time, the HashMap is increasing, its using more memory and the minting thread uses ~ double the cpu time. when it reached sz=33554432, it usesd 70%. once it reaches 58720256 its 100% obviously. unfortunately now emercoind is deadlocked. it wont respond to any calls nor kill signals (have to kill with -SIGKILL/-9). after waiting 10-15 min, it responds again.
This should be improved. Im waiting to see how long the next increase will take, this implementation is horribly slow and is blocking everything...