[Bug]: Crash: free(): invalid next size (fast) #3267
Comments
|
Not had a report of this before. Is it reproducable? ie, if you did it again, does it occur again? |
|
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? |
|
No. There is only the logging in the 'Log' panel, showing commands sent to sqlite and the return results. |
|
Yes, and I faced a crash in 3.12.2 that was fixed on master ;) |
|
Yeah, the "need to be able to trigger it again" thing is kind of a pain. Not much choice though. 😉 |
|
Again, I had an error in my custom SQL query and wanted to switch to the data tab: |
|
My first impression is that not everything was compiled against the same
version of QT.
…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:
***@***.***>
|
|
As far as i can tell ( |
|
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?
From
[this](https://packages.debian.org/search?keywords=qt5&searchon=names&suite=all§ion=all),
that tells me you're on on Debian Stable (Bullseye). That DB4S is
choking on QtCore is disconcerting. You installed DB4S from Debian
packaging?
|
|
FWIW, Debian stable has DB4S at an old version 3.12.1. @Jonny007-MKD, Can you confirm your version of application, please? |
|
True, I am running Linux Mint LMDE which is based on Bullseye. |
|
Another segfault when switching tabs (from Data to Execute SQL I believe) |
|
Interesting. Would you be ok to paste the output of 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. |
|
Sure :) |
|
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What did you do?
I wrote some query using some left joins, then clicked on the "Browse Data" tab. In this moment, DB4S crashes
What did you expect to see?
No crash
What did you see instead?
The only output on the console:
DB4S Version
Today's master (496d39d)
What OS are you seeing the problem on?
Linux
OS version
Linux Mint LMDE Bullseye
Relevant log output
No response
Prevention against duplicate issues
The text was updated successfully, but these errors were encountered: