-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Crash in mdb_cursor_get while syncing #724
Comments
when it crashes there, can you "print *mc" and paste that output too? |
Will do so when it happens again. |
So your current progress was 678888, but it crashed 3 times on the way to getting there? what block height did you start at? |
Yesterday after the blockchain conversion the first log entry was:
Just noticed this in the log too (but no crash):
I suppose something went wrong in the conversion and it'd be better to start over. |
I'm seeing the |
I removed the
I have the following output
Will keep the gdb session running in case there's more you want to debug. |
Thanks. are you on IRC? |
In frame 1: |
(pretty sure this crash is already fixed in current master 240a50f) |
Currently not on IRC, will be on later. Result:
|
Ok, will try to upgrade to latest master and rebuild. |
Aside from the crash fix, there are some remaining glitches that I believe are cleaned up in #727 |
Been running with #727 for almost a day no, no crashes. |
Up to three times now I've had crashes (SIGSEGV) during sync.
blockchain_export
/blockchain_import
.Ubuntu 14.04.4 LTS
VM, 64-bit, 8GB memory, 8 cores, still plenty of HD space leftRelWithDebInfo
modegdb output (#1-#5):
Full gdb traceback can be found here:
http://0bin.net/paste/pqduymi1W8k9cbZY#QkhwEmaE1oxMAJpke32hpEjeiXxhmMrhXm8qY-gqRQE
The text was updated successfully, but these errors were encountered: