I have a similar problem with Mixxx from a quite recent 2.3 branch (I'm using https://github.com/mixxxdj/mixxx/commit/9564ac2837bdfbda385edc581b70e4c8309c7f96).
When I try to remove a cue point, Mixxx crashes with SIGSEGV. This happens only occasionally, in my case as far as I remember while deck 1 is playing and deleting the cue point on deck2 (don't know if this relevant or has an impact). Unfortunately I'm not able to reproduce this every time when I'm deleting cue points. But I've managed to get a backtrace, maybe this could help you to solve this issue:
Core was generated by `mixxx'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fa43acc94b7 in QMutex::lock() () from /usr/lib64/libQt5Core.so.5
[Current thread is 1 (Thread 0x7fa434aee9c0 (LWP 3665))]
(gdb) bt
#0 0x00007fa43acc94b7 in QMutex::lock() () at /usr/lib64/libQt5Core.so.5
#1 0x0000558fdf5ecd17 in Cue::getHotCue() const ()
#2 0x0000558fdf2e4724 in WOverview::updateCues(QList<CuePointer> const&) ()
#3 0x0000558fdf2e50d3 in WOverview::onMarkChanged(double) ()
#4 0x00007fa43aea5eaf in () at /usr/lib64/libQt5Core.so.5
#5 0x0000558fdf3aba20 in ControlProxy::valueChanged(double) ()
#6 0x00007fa43ae9e0ef in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#7 0x00007fa43dbbe6df in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#8 0x00007fa43ae73908 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#9 0x00007fa43ae76dee in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#10 0x00007fa43aec42c3 in () at /usr/lib64/libQt5Core.so.5
#11 0x00007fa43d00c92c in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#12 0x00007fa43d00cbd8 in () at /usr/lib64/libglib-2.0.so.0
#13 0x00007fa43d00cc8f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#14 0x00007fa43aec3d68 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#15 0x00007fa43ae7239b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#16 0x00007fa43ae7a6d0 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#17 0x0000558fdf142ee3 in main ()
I have to mention, that I'm using my Denon MC7000 controller to set and delete the cue points, and Gentoo Linux x86_64 with kernel 5.10.110.
I have a similar problem with Mixxx from a quite recent 2.3 branch (I'm using https:/ /github. com/mixxxdj/ mixxx/commit/ 9564ac2837bdfbd a385edc581b70e4 c8309c7f96).
When I try to remove a cue point, Mixxx crashes with SIGSEGV. This happens only occasionally, in my case as far as I remember while deck 1 is playing and deleting the cue point on deck2 (don't know if this relevant or has an impact). Unfortunately I'm not able to reproduce this every time when I'm deleting cue points. But I've managed to get a backtrace, maybe this could help you to solve this issue:
Core was generated by `mixxx'. libQt5Core. so.5 libQt5Core. so.5 :updateCues( QList<CuePointe r> const&) () :onMarkChanged( double) () libQt5Core. so.5 :valueChanged( double) () :event( QEvent* ) () at /usr/lib64/ libQt5Core. so.5 vate::notify_ helper( QObject* , QEvent*) () at /usr/lib64/ libQt5Widgets. so.5 n::notifyIntern al2(QObject* , QEvent*) () at /usr/lib64/ libQt5Core. so.5 nPrivate: :sendPostedEven ts(QObject* , int, QThreadData*) () at /usr/lib64/ libQt5Core. so.5 libQt5Core. so.5 context_ dispatch () at /usr/lib64/ libglib- 2.0.so. 0 libglib- 2.0.so. 0 context_ iteration () at /usr/lib64/ libglib- 2.0.so. 0 rGlib:: processEvents( QFlags< QEventLoop: :ProcessEventsF lag>) () at /usr/lib64/ libQt5Core. so.5 :exec(QFlags< QEventLoop: :ProcessEventsF lag>) () at /usr/lib64/ libQt5Core. so.5 n::exec( ) () at /usr/lib64/ libQt5Core. so.5
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fa43acc94b7 in QMutex::lock() () from /usr/lib64/
[Current thread is 1 (Thread 0x7fa434aee9c0 (LWP 3665))]
(gdb) bt
#0 0x00007fa43acc94b7 in QMutex::lock() () at /usr/lib64/
#1 0x0000558fdf5ecd17 in Cue::getHotCue() const ()
#2 0x0000558fdf2e4724 in WOverview:
#3 0x0000558fdf2e50d3 in WOverview:
#4 0x00007fa43aea5eaf in () at /usr/lib64/
#5 0x0000558fdf3aba20 in ControlProxy:
#6 0x00007fa43ae9e0ef in QObject:
#7 0x00007fa43dbbe6df in QApplicationPri
#8 0x00007fa43ae73908 in QCoreApplicatio
#9 0x00007fa43ae76dee in QCoreApplicatio
#10 0x00007fa43aec42c3 in () at /usr/lib64/
#11 0x00007fa43d00c92c in g_main_
#12 0x00007fa43d00cbd8 in () at /usr/lib64/
#13 0x00007fa43d00cc8f in g_main_
#14 0x00007fa43aec3d68 in QEventDispatche
#15 0x00007fa43ae7239b in QEventLoop:
#16 0x00007fa43ae7a6d0 in QCoreApplicatio
#17 0x0000558fdf142ee3 in main ()
I have to mention, that I'm using my Denon MC7000 controller to set and delete the cue points, and Gentoo Linux x86_64 with kernel 5.10.110.
Kind regards,
Marco