masternode debug on inactive masternode may result in deadlock of threads

[ciripel]

Failed to verify masternode status internal error.
Confirmed not modified masternode returned this error after some time.
Not capable masternode: Could not find suitable coins!
looks like nodes get stuck after losing coins
some time after that

based on above output
all problematic nodes got into fcked up state after improper activation
you can ignore crossed nodes, these 2 works
others will have to be probably added again and users will have to provide new mnkeys and new outputs
...
alright
I believe that this is related to activation because everything else is activated
and works without issues
so this is most probable scenario right now
...

looks like issue may be in new getblocktemplate

this is where are stuck nodes looping:
https://github.com/TENTOfficial/TENT/blob/master/src/bitcoind.cpp#L45
here is wallet thread: https://github.com/TENTOfficial/TENT/blob/master/src/wallet/walletdb.cpp#L1083
msg handler thread: https://github.com/TENTOfficial/TENT/blob/master/src/main.cpp#L6239
opencon thread: https://github.com/TENTOfficial/TENT/blob/master/src/main.cpp#L308
addcoin thread same as opencon
snowgem-net thread: https://github.com/TENTOfficial/TENT/blob/master/src/main.cpp#L336
obfusca thread: https://github.com/TENTOfficial/TENT/blob/master/src/wallet/wallet.cpp#L4042
scriptc thread: https://github.com/TENTOfficial/TENT/blob/master/src/checkqueue.h#L102
all 14 or 15 scriptc threads are on same line
so deadlock

If we find more we add more info.