Quote from: Riseman on December 19, 2013, 11:59:25 AM

1. Sync problem

After starting the client it can't sync ("No block source available"). Reproduced behind NAT. Sometimes you simply have to wait 10-30 min. and it syncs. Sometimes it doesn't. Adding lots of nodes from this thread to the memorycoin.conf file seems to fix this issue.

Also sometimes the client appears to be synced but the block count is less than real block count. Improves after some time or after restart.

Okay - this should be resolved. We've got some high capacity nodes now in the client, and reduced the default number of outbound connections to 4. This should help with getting new clients started and reduce the stress on the network.

Quote from: Riseman on December 19, 2013, 11:59:25 AM

2. Program crash

Usually happens when you turn mining on and off several times or change thread count. For example: Mine 4 Processes -> Mine 2 Processes -> Switch Mining Off -> Mine 4 Processes -> crash. I noticed that you have to wait for some time for mining to actually stop before enabling it again but it doesn't prevent crashes. Sometimes the crash is followed by database corruption.

Haven't investigated this yet. It does take a cycle to change the number of processes, so recommend you don't do multiple changes too rapidly. Decide how many processes and stick with it for now.

Quote from: Riseman on December 19, 2013, 11:59:25 AM

3. Database corruption

Happens after number 3. After starting the client it shows a dialog like "Do you want to rebuild index?" Then it reindexes the database.

So this is more a symptom of another problem than a problem itself.

Quote from: Riseman on December 19, 2013, 11:59:25 AM

4. Mining stops

After mining for some time it stops. Enabling mining with any number of threads doesn't work even if the blockchain is in sync and with correct block count. Restarting client fixes this.

Okay - I've got a new watchdog timer in there to recover from this. If threads seem to be behind by more than 60 seconds, it'll reset.

Quote from: Riseman on December 19, 2013, 11:59:25 AM

5. The application doesn't close

Usually happens after number 4. After closing the client window memorycoin-qt.exe can still be seen in the process list.

Again, this is a symptom of a problem, rather than a problem itself.

So new binaries are available, and the source updated. Thanks again for the detailed bug report.