Closed mr-tron closed 6 years ago
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). i686 arch last official release 0.12.1.5 binary from dash.org Dash QT crashes 2-3 times every day.
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 Continuing.
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7efd977fe700 (LWP 3461)] __pthread_mutex_trylock (mutex=0x1f0) at ../nptl/pthread_mutex_trylock.c:43 43 ../nptl/pthread_mutex_trylock.c: No such file or directory. (gdb) bt
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.