Windows client crashes when mining

[d5000]

From the bugs we talked about in Bitcointalk:
Windows client 0.3.2.1-alpha seems to crash randomly when mining is enabled.

See posts:
https://bitcointalk.org/index.php?topic=613213.msg11965355#msg11965355
https://bitcointalk.org/index.php?topic=613213.msg11980376#msg11980376

[ryanwhitehouse]

Hi there,

I just started mining slim coin and really enjoying it so far! Love the POB / POW / POS hybrid.

I am running the mining client on windows and was running fine for about 24 hours and now it seems to crash every minute or so, kind of ruining my mining.

Is there any more information about this? / Any idea why it crashes? I am a software developer and happy to try and fix it with some direction if possible. Is there a bounty to solve this?

Thanks,
Ryan

[ryanwhitehouse]

Thought I should add, it's definitely related to proof of burn. I burnt coins just before this started happening and now I'm unable to mine and have burn going at the same time.

I have done a little bit of digging and it looks like if I don't have any money burnt (ie, the wallet is fresh) then I will be able to mine again. I think I am getting a much better rate currently with mining than burning so if I had to choose, I would mine and not burn, maybe save up a bunch so when I do have some burnt, it is at least a decent amount and will give me good returns.

As a work around I can use two computers and mine on one, send it to my other address and do proof of burn on that. However I don't know how to get from my position now to that. I need to mine on this computer, so is there a way that I can log on to this wallet / keep my coins already mined and use the money that I have already burnt. Then reset this wallet / lose everything and start mining from scratch on this one. Do I just need to use my secret phrase on a fresh wallet on my other computer to import this one, and then somehow delete / clear this wallet back to a fresh state. Is there an explicit import wallet function to move from one computer to another?

Also, could we please add a warning somewhere obvious for windows users not to burn coins until this is fixed? This is a severe issue that has prevented me mining for a few hours, and suspect a couple of days before I get this sorted. I had a really good experience so far with the documentation and this coin, but this is a huge hurdle that I think should be fixed asap.

Again, I am happy to debug / fix this issue or at least help diagnose or fix it. Is there a developer that could get in touch with me about how to set up my environment so I could help? Really keen to start mining again I think this coin is awesome!

[d5000]

Hi,
to sort out one known problem: Are you also "staking" while mining? You can disable staking by setting a high reservebalance value (e.g. reservebalance=9999999, it should be higher to the maximum coins you expect to have in your wallet) in the slimcoin.conf configuration file. If you have a zero or low reservebalance value, then staking could be the responsible for the high memory consumption, even if you have few coins in your wallet. Read more here:

http://slimco.in/proof-of-stake-guide/#cpu-and-memory-usage

Unfortunately, this is a "systemic" problem (as far as I know, it's related to the DCrypt algorithm), so staking and mining/burning at the same time with the current client is not recommended, because if you receive rewards (PoB, PoW or PoS) your wallet will contain a higher number of inputs and thus will consume more memory.