Quote from: d5000 on January 27, 2015, 03:44:02 PM

Thanks Mr. E! I have compiled your fork and it worked without errors. If I remember right the error you mention (ambiguous type conversion) was also the one that prevented me from compiling a123's last code.

I had a Slimcoin crash recently but that was because I was running it with very low memory & swap after a reboot.

That's good to hear. Did you pull my whole github fork, or just make the change I gave to a123's version?

I seem to have gotten rid of the slimcoin-qt crashes by compiling a version which is more aggressive at banning 'old version' clients (ones that keep spamming getblocks requests). This suggests that the crash is due to dealing with large numbers of requests in close proximity or something similar - which would be consistent with what I've seen where the memory usage suddenly spikes upwards before a crash. I'm just not sure about pushing that pach out widely, since I don't know what the chances are of it banning a legitimate node by accident. I am still showing 27 active connections, though, which suggests it hasn't banned everyone (yet?).

I don't know if slimcoin on linux has the same problem; as far as I know, I'm the only one reporting issues with this and I'm mainly running the Windows client. (I should try running a linux one too and see how it goes.)

Quote from: masterOfDisaster on January 27, 2015, 10:29:24 PM

The trouble with PoS at Slimcoin might be related to memory issues or strange behaviour with the interaction of the 3 processes.
I don't remember exactly, although I've read almost the whole thread, but I think there were some posts regarding the PoS issues.
After all that was the reason for a123 to disable PoS (by adjusting the default configuration), right?

Yes, it was changed so by default it has a 'reserve balance' of like 10,000,000 or something, so it won't stake coins unless you have more than that. But PoS blocks are still accepted, and you can still re-enable staking in the debug console (by setting 'reservebalance false'), which I've done and haven't seen any problems so far. If I have time, I should go back and look over the old posts to try and figure out what exactly the problem was... (or someone else could if they're feeling bored!)