-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux client gets stuck at certain blocks #1
Comments
422195 was definitively the same problem. Up to the actual value, there were two more blocks where the client gets stuck. |
I don't know whether this is related ... IIRC, the code was never released per se but made available for trial. I had a go at putting the sources on more a stable footing, in a more publicly accessible repos (which seems to have some mild success) but the rebasing on latest PPCoin sources was very much speculative effort and (as far as I understood it) prompted little interest (not entirely surprising to me). So there was no opportunity to engage potential adopters in the nitty-gritty of hard/soft forks and all the administrivia that are attendant, of which the above code is just one example. |
Unfortunately I don't have the technical knowledge to give you a qualified answer. Do you mean that your commit could be the reason for the client getting stuck, or that it can be the solution? The error is appearing also in all old 0.3 versions. BTW, your work is much appreciated, if we manage to get other devs on board it can be a good starting point. If there is something to be done not related directly to coding (alpha/beta testing, etc.) I can help. |
This is currently affecting me as well. |
From the bugs we talked about in Bitcointalk:
Linux client 0.3.2 gets stuck at certain blocks when downloading the blockchain. If redownloading, it gets stuck too.
The last block where I encountered the problem and can confirm it was block 311792.
I got stuck recently at 422195, but must confirm if it's because of the same problem.
Windows QT client does not have the problem, even when using Wine.
The text was updated successfully, but these errors were encountered: