-
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
sometimes dash-qt crashes #1519
Comments
What version of Ubuntu are you running (lsb_release -a) ? Also did you build dash-qt yourself or use the official binary ? |
I running whonix (binary it`s debian 8 jessie with some special configs). |
I am also seeing most likely the same issue. Crashes are always related to Darksend (ie. coin mixing). Debian/8.9 here (jessie), with libboost-1.55 from .debs. Compiled with --with-incompatible-bdb, and with debug symbols. Host is x86_64 kvm-based vps but this happens even on bare metal (tested). I managed to get a stack trace by attaching gdb to the dashd process. By looking at the trace and the source code, it makes me think some pointers are getting corrupted somewhere. (gdb) continue Program received signal SIGSEGV, Segmentation fault. |
I gave more memory to virtual machine and crashes gone. But it wasn`t OOM. |
I took off "-disablewallet" switch from my dashd command line params, and now the crashes are mysteriously gone. |
Obsolete |
dash-qt: /home/ubuntu/build/dash/depends/i686-pc-linux-gnu/share/../include/boost/thread/pthread/recursive_mutex.hpp:113: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.
always during mixing via tor proxy.
The text was updated successfully, but these errors were encountered: