You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Crash: free(): invalid next size (fast) #3267
No, I couldn't reproduce it in the last 20 minutes. Can I start the app with some verbose logging or stack traces or something?
The database is local on my Ext4 filesystem.
No. There is only the logging in the 'Log' panel, showing commands sent to sqlite and the return results.
We've not had reports of this before, so I'd lean towards it being an odd-ball case.
Typing in the execute SQL window has no bearing on the 'browse data' tab, unless of course the SQL amends the schema (add, delete tables, etc) but not in the middle of typing.
Linux is a weird beast, and you've done the right thing compiling from master. Thats a slightly different codebase than the 3.12.2 release (or earlier) that some distros have in their packages. 3.12.2 is getting quite old now...
Yes, and I faced a crash in 3.12.2 that was fixed on master ;)
I think I'm going to run DB4S in gdb for the next time. Maybe it at least reveals some stack or so.
Again, I had an error in my custom SQL query and wanted to switch to the data tab:
Thread 1 "sqlitebrowser" received signal SIGSEGV, Segmentation fault.
0x00007ffff67075e3 in QHashData::free_helper(void (*)(QHashData::Node*)) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb) bt
#0 0x00007ffff67075e3 in QHashData::free_helper(void (*)(QHashData::Node*)) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#1 0x00007ffff761d5f0 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#2 0x00007ffff7604f25 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#3 0x00007ffff7605014 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4 0x00007ffff7605014 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5 0x00007ffff760514c in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6 0x000055555579ff81 in TableBrowserDock::setFocusStyle(bool) (this=<optimized out>, on=on@entry=false)
at build/sqlitebrowser/src/TableBrowserDock.cpp:62
#7 0x000055555567776a in MainWindow::changeTableBrowserTab(TableBrowserDock*)
(this=0x555555dfc950, dock=0x555556392c90) at build/sqlitebrowser/src/MainWindow.cpp:3906
#8 0x000055555567798a in MainWindow::dataTableSelectionChanged(QModelIndex const&) (this=0x555555dfc950, index=...)
at build/sqlitebrowser/src/MainWindow.cpp:1083
#9 0x00007ffff68e45a6 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007ffff6848ba5 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector<int> const&) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00005555556e37d2 in SqliteTableModel::handleFinishedFetch(int, unsigned int, unsigned int)
(this=0x5555564e1a40, life_id=<optimized out>, fetched_row_begin=0, fetched_row_end=3)
at build/sqlitebrowser/src/sqlitetablemodel.cpp:83
#12 0x00007ffff68d9ff1 in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007ffff756315f in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007ffff68adfca in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007ffff68b0a01 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007ffff6905e93 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007ffff5a5ee6b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007ffff5a5f118 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ffff5a5f1cf in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007ffff690551f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007ffff68ac98b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007ffff68b4c00 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00005555555f76ab in main(int, char**) (argc=<optimized out>, argv=<optimized out>)
at build/sqlitebrowser/src/main.cpp:63
On 2023-01-30 09:49, Jonny007-MKD wrote:
Again, I had an error in my custom SQL query and wanted to switch to
the data tab:
|Thread 1 "sqlitebrowser" received signal SIGSEGV, Segmentation fault.
0x00007ffff67075e3 in QHashData::free_helper(void
(*)(QHashData::Node*)) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb) bt #0 0x00007ffff67075e3 in QHashData::free_helper(void
(*)(QHashData::Node*)) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #1
0x00007ffff761d5f0 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#2 0x00007ffff7604f25 in () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #3 0x00007ffff7605014 in ()
at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #4 0x00007ffff7605014 in
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x00007ffff760514c
in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6
0x000055555579ff81 in TableBrowserDock::setFocusStyle(bool)
(this=<optimized out>, ***@***.***=false) at
build/sqlitebrowser/src/TableBrowserDock.cpp:62 #7 0x000055555567776a
in MainWindow::changeTableBrowserTab(TableBrowserDock*)
(this=0x555555dfc950, dock=0x555556392c90) at
build/sqlitebrowser/src/MainWindow.cpp:3906 #8 0x000055555567798a in
MainWindow::dataTableSelectionChanged(QModelIndex const&)
(this=0x555555dfc950, index=...) at
build/sqlitebrowser/src/MainWindow.cpp:1083 #9 0x00007ffff68e45a6 in
() at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007ffff6848ba5 in
QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex
const&, QVector<int> const&) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x00005555556e37d2 in
SqliteTableModel::handleFinishedFetch(int, unsigned int, unsigned int)
(this=0x5555564e1a40, life_id=<optimized out>, fetched_row_begin=0,
fetched_row_end=3) at build/sqlitebrowser/src/sqlitetablemodel.cpp:83
#12 0x00007ffff68d9ff1 in QObject::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x00007ffff756315f in
QApplicationPrivate::notify_helper(QObject*, QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x00007ffff68adfca in
QCoreApplication::notifyInternal2(QObject*, QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x00007ffff68b0a01 in
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x00007ffff6905e93 in
() at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007ffff5a5ee6b in
g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007ffff5a5f118 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ffff5a5f1cf in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007ffff690551f in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x00007ffff68ac98b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x00007ffff68b4c00 in
QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00005555555f76ab in main(int, char**) (argc=<optimized out>,
argv=<optimized out>) at build/sqlitebrowser/src/main.cpp:63 |
—
Reply to this email directly, view it on GitHub
<#3267 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABTAO2676G33EWYJFKBXOYLWU7WIVANCNFSM6AAAAAAUGYSF4E>.
You are receiving this because you are subscribed to this
thread.Message ID:
***@***.***>
On 2023-01-30 10:01, Jonny007-MKD wrote:
As far as i can tell (|dpkg -l | grep qt|) I only have Qt version
5.15.2 installed. Is there anything else I should check?
True, I am running Linux Mint LMDE which is based on Bullseye.
Due to some other bugs in 3.12.1 I built DB4S myself from current master (commit 496d39d).
Another segfault when switching tabs (from Data to Execute SQL I believe)
Thread 1 "sqlitebrowser" received signal SIGSEGV, Segmentation fault.
0x00007ffff6707803 in QHashData::nextNode(QHashData::Node*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb) bt
#0 0x00007ffff6707803 in QHashData::nextNode(QHashData::Node*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#1 0x00007ffff6dc5435 in () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#2 0x00007ffff6dc5538 in () at /lib/x86_64-linux-gnu/libQt5Gui.so.5
#3 0x00007ffff68d9f2f in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x00007ffff756315f in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5 0x00007ffff68adfca in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007ffff69048e3 in QTimerInfoList::activateTimers() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007ffff690519c in () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007ffff5a5ee6b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x00007ffff5a5f118 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007ffff5a5f1cf in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007ffff690551f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007ffff68ac98b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007ffff68b4c00 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00005555555f76ab in main(int, char**) (argc=<optimized out>, argv=<optimized out>)
at build/sqlitebrowser/src/main.cpp:63
Activity
chrisjlocke commentedon Jan 25, 2023
Not had a report of this before. Is it reproducable? ie, if you did it again, does it occur again?
Is the database local, or in some wacky filesystem?
Jonny007-MKD commentedon Jan 25, 2023
No, I couldn't reproduce it in the last 20 minutes. Can I start the app with some verbose logging or stack traces or something?
The database is local on my Ext4 filesystem.
chrisjlocke commentedon Jan 26, 2023
No. There is only the logging in the 'Log' panel, showing commands sent to sqlite and the return results.
We've not had reports of this before, so I'd lean towards it being an odd-ball case.
Typing in the execute SQL window has no bearing on the 'browse data' tab, unless of course the SQL amends the schema (add, delete tables, etc) but not in the middle of typing.
Linux is a weird beast, and you've done the right thing compiling from master. Thats a slightly different codebase than the 3.12.2 release (or earlier) that some distros have in their packages. 3.12.2 is getting quite old now...
Jonny007-MKD commentedon Jan 27, 2023
Yes, and I faced a crash in 3.12.2 that was fixed on master ;)
I think I'm going to run DB4S in gdb for the next time. Maybe it at least reveals some stack or so.
justinclift commentedon Jan 28, 2023
Yeah, the "need to be able to trigger it again" thing is kind of a pain. Not much choice though. 😉
Jonny007-MKD commentedon Jan 30, 2023
Again, I had an error in my custom SQL query and wanted to switch to the data tab:
scottfurry commentedon Jan 30, 2023
Jonny007-MKD commentedon Jan 30, 2023
As far as i can tell (
dpkg -l | grep qt) I only have Qt version 5.15.2 installed. Is there anything else I should check?scottfurry commentedon Jan 30, 2023
scottfurry commentedon Jan 30, 2023
FWIW, Debian stable has DB4S at an old version 3.12.1. @Jonny007-MKD, Can you confirm your version of application, please?
Jonny007-MKD commentedon Jan 30, 2023
True, I am running Linux Mint LMDE which is based on Bullseye.
Due to some other bugs in 3.12.1 I built DB4S myself from current master (commit 496d39d).
Jonny007-MKD commentedon Jan 30, 2023
Another segfault when switching tabs (from Data to Execute SQL I believe)
justinclift commentedon Jan 30, 2023
Interesting. Would you be ok to paste the output of
lddfor your compiled sqlitebrowser executable?eg on my system here, it's:
With that, we can take a look a the paths to the Qt libraries it's using, and see if anything strange is showing up.
Jonny007-MKD commentedon Jan 31, 2023
Sure :)
justinclift commentedon Feb 1, 2023
Hmmm, nothing looks obviously out of place there. So, doesn't seem like a mismatched Qt library (or similar) being the problem.
This is feeling like a bug, more than some kind of system configuration problem.
Jonny007-MKD commentedon Jan 15, 2026
I'm seeing segfaults again in
QHashData::nextNode()(for a complete call stack see #4085).I'm running LMDE 7 and the latest version of sqlitebrowser of Debian (3.13.0-1+b1, in About: 3.13.99 (Apr 11 2025), Qt Version 5.15.15).