-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 ProcessMessages, 0.12.0.58 #933
Comments
Thanks for submitting, the debug.log does not help much though. The interesting part is
but it doesnt tell much :-) |
Was your node running on a machine with a quite small amount of memory ? This looks the kind of error one would see if the process ran out of memory. |
It has 1Gb of memory and the process have never exceeded 500Mb, so it wouldn't fail unless the process was trying to allocate 500Mb, which feels unlikely. |
Is this repeatable at all, or did it only happen once ? |
I still think it's probably memory exhaustion. This certainly wasn't the only running process and the kernel needs memory too. 1 GB may be just too tight for all this unless you have swap space enabled (but that might be very slow if more memory is actually needed often). |
Only happened once. |
From
~/.dash/debug.log
. Unfortunately it's the only information I have.The text was updated successfully, but these errors were encountered: