bitcoin-qt usually SEGVs when exited using unix signals

rebroad commented at 2:03 pm on May 2, 2012: contributor

This doesn’t happen if it’s quit using the GUI (speaking of which, often the tray icon does not appear, so it cannot be exited using the GUI the majority of the time).

Version is 0.6.1rc1 with some modifcations (which shouldn’t be the cause, IMHO) - can be reviewed on my github fork.

Output from gdb:-

Program received signal SIGHUP, Hangup. 0x00007ffff498d473 in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) continue Continuing. [Thread 0x7fffe7e10700 (LWP 20463) exited] [Thread 0x7fffdee43700 (LWP 20480) exited] [Thread 0x7fffdbe3d700 (LWP 20476) exited] [Thread 0x7fffdc63e700 (LWP 20475) exited] [New Thread 0x7fffdc63e700 (LWP 28808)] [Thread 0x7fffdc63e700 (LWP 28808) exited]

Program received signal SIGSEGV, Segmentation fault. 0x0000000000a2b630 in ?? () (gdb) bt #0 0x0000000000a2b630 in ?? () #1 0x00007ffff56e3432 in QString::vsprintf(char const_, _va_list_tag) ()

from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x00007ffff569179c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x00007ffff5691f54 in qWarning(char const*, …) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x00007ffff5780fce in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) ()

from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x00007ffff5785789 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00000000004286d7 in main (argc=1, argv=) at src/qt/bitcoin.cpp:282

(gdb)

Also, sometimes (not always) the output to stdout upon exit will make mention of some Qt programming error, something about not catching something in the right thing. I’ll update this issue with the exact message when I next see it.

rebroad commented at 6:35 pm on May 2, 2012: contributor

Here is another gdb output, this one seeming to look quite different:

Program received signal SIGSEGV, Segmentation fault. 0x00007ffff6243958 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (gdb) bt #0 0x00007ffff6243958 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #1 0x00007ffff62446e3 in QSortFilterProxyModel::index(int, int, QModelIndex const&) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #2 0x00007ffff6241469 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #3 0x00007ffff62451a7 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #4 0x00007ffff623f232 in QAbstractProxyModel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #5 0x00007ffff62483e5 in QSortFilterProxyModel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #6 0x00007ffff5794eba in QMetaObject::activate(QObject_, QMetaObject const_, int, void*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007ffff579536f in QObject::destroyed(QObject) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007ffff5798ef7 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x000000000043c589 in AddressTableModel::~AddressTableModel (this=, __in_chrg=) at src/qt/addresstablemodel.cpp:86 #10 0x0000000000000000 in ?? ()

rebroad commented at 10:44 pm on May 2, 2012: contributor

This is the Qt error sometimes seen as mentioned earlier:-

Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there.

laanwj commented at 6:13 am on May 3, 2012: member

speaking of which, often the tray icon does not appear, so it cannot be exited using the GUI the majority of the time

Huh? I’ve never heard this before, and also never experienced this. Together with #1183 it seems that your desktop is somehow broken.

rebroad commented at 11:35 am on May 3, 2012: contributor

@laanwj - If I’m the only experiencing this, then it would seem that it’s a rare combination between my unusual desktop, and something unusual bitcoin-qt is doing (since no other applications have these problems). I’d still suggest this issue remains open pending further investigation - and if anyone has any advice on how to debug this, I’d be happy to help. I’m shortly planning to upgrade from Oneiric to Precise, so perhaps that will fix the problem. I don’t believe my desktop has had any unusual configuration changes. It’s pretty much a stock Oneiric AFAIK.

laanwj commented at 6:17 pm on May 13, 2012: member

0This doesn't happen if it's quit using the GUI (speaking of which, often the tray icon does not appear, so it cannot be exited using the GUI the majority of the time).

Can you try with -nosplash? It seems that the splash screen causes unity to be confused if there is a .desktop file, as it regards it as the main window (that disappears).

laanwj commented at 7:57 am on June 12, 2012: member

Can you test whether this is fixed with #1439?

TheBlueMatt commented at 7:26 pm on June 12, 2012: member

Bitcoin-Qt has virtually always done this (if its working while you exit), but it is fixed by #1439.

laanwj closed this on Jun 14, 2012

suprnurd referenced this in commit bc3b349cc1 on Dec 5, 2017

lateminer referenced this in commit 7299031b85 on Jan 22, 2019

MarcoFalke locked this on Sep 8, 2021

bitcoin-qt usually SEGVs when exited using unix signals #1182