SQLite DB Browser quits on table data Browse tab refresh

[dragonstar0828]

Details for the issue

What did you do?

Have DB Browser for SQLite 3.12.2 running on a Windows 10 64-bit laptop.

Have a database open looking some table data in the Browse tab.

Have Delphi 10.2 app running connected to the same db using Unidac from DevArt.

Updated an existing record in my app, click the Refresh button in the Browse tab.

What did you expect to see?

The grid refreshed with the updated data.

What did you see instead?

The application quit with no error messages and left the db in a locked state.

Useful extra information

DB4S v3.12.2 [built for x86_64-little_endian-llp64] on Windows 10 (10.0) (winnt/10.0.19044) [x86_64]
using SQLite Version 3.35.5
and Qt 5.12.8

[chrisjlocke]

Interesting. I have applications connected to databases all the time with no effect.
Its possible that your application locks the database against other applications reading? I've not tried this. Usually if this occurs, DB4S reports the database is 'locked' (I've had that before).

I assume this is reproducable 100% of the time? (ie, hasn't just happened once).

[dragonstar0828]

It's possible that your application locks the database against other applications reading? I'm not aware of doing any explicit locking, I can check the options in the UniDac connection object and see if I see anything about locking. I assume this is reproducable 100% of the time? (ie, hasn't just happened once) Yep, every time I do anything with the db and click that Refresh it just quits with no error messages. drc :)

[dragonstar0828]

Better. The default connection option for locking is Exclusive, I set it to Normal and everythingseems happy now. However, if it is locked the perhaps your app should pop up some dialog instead of just quittingwhen one tries to browse the data? Thanks for your quick response! drc :)

[chrisjlocke]

Thanks for replying back. It's possible DB4S isn't expecting the file to be locked and as such doesn't know what to do so cries in a heap.
Unfortunately, our developers aren't Windows developers and each OS locks files in a different way, so it's possible this may not be reproducable by them. I don't know though. Hopefully they can write some code which locks the database to see if it upsets DB4S.
Just for confirmation, is the database local to DB4S/the computer, or is it on a network or some weird file system at all?

[dragonstar0828]

Just for confirmation, is the database local to DB4S/the computer, or is it on a network or some weird file system at all? The database, my app and your app are all running local on my Windows 10 64-bit laptop - no networks, no shared drives, no vpn's, no vm's, no nothing. drc :)

[chrisjlocke]

Excellent - thanks fdor the confirmation. Just helps reproduce and identify the issue.

[dragonstar0828]

Would think someone there is using Windows, otherwise you couldn't produce a Windows executable and an installer. Just me thinking out loud... :)

[chrisjlocke]

It's written in C++ and Qt, so it's just compiled on a Windows VM overnight. Automation is a wonderful thing. ;)
This means it's cross-platform (Linux, Mac and Windows) but just one code-base - spread the love across the operating systems.
I think I'm the only one of us in the main team that uses Windows in anger, but I don't produce any code ... so I'm not useful in that regard 😂

[MKleusberg]

Ok, so here's a note to myself how to reproduce this:

1. Open the DB in DB4S
2. Open the DB in the sqlite3 command line tool
3. Run pragma locking_mode=exclusive; in the command line tool
4. Make a change to the database via the command line tool
5. Refresh the database in DB4S

Interestingly it doesn't crash for me though. The only thing is that it doesn't show any data. @dragonstar0828 Is it possible for you to update to the latest nightly build and check if it stops crashing for you too? Not showing any data sure isn't correct here either but depending on whether the current version is crashing on some systems or not the fix might be different.

[dragonstar0828]

Hey Martin - if you point me at the nightly builds area I'll give it a try the first of the week when I have a moment at work to look into it. Though first I'll have to remember how to produce the original crash on my side... drc :)

…

-----------------------------------------From: "Martin Kleusberg" To: "sqlitebrowser/sqlitebrowser" Cc: "dragonstar0828", "Mention" Sent: Saturday March 19 2022 3:32:14PM Subject: Re: [sqlitebrowser/sqlitebrowser] SQLite DB Browser quits on table data Browse tab refresh (Issue #2979) Ok, so here's a note to myself how to reproduce this: * Open the DB in DB4S * Open the DB in the sqlite3 command line tool * Run pragma locking_mode=exclusive; in the command line tool * Make a change to the database via the command line tool * Refresh the database in DB4S Interestingly it doesn't crash for me though. The only thing is that it doesn't show any data. @dragonstar0828 [1] Is it possible for you to update to the latest nightly build and check if it stops crashing for you too? Not showing any data sure isn't correct here either but depending on whether the current version is crashing on some systems or not the fix might be different. — Reply to this email directly, view it on GitHub [2], or unsubscribe [3]. Triage notifications on the go with GitHub Mobile for iOS [4] or Android [5]. You are receiving this because you were mentioned.Message ID: Links: ------ [1] https://github.com/dragonstar0828 [2] #2979 (comment) [3] https://github.com/notifications/unsubscribe-auth/AFK3UQUADM22ZLUUL5HZZPTVAY2U3ANCNFSM5OLQ5IIA [4] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [5] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

[chrisjlocke]

the nightlies are here.
https://nightlies.sqlitebrowser.org/latest/

Download this zip
https://nightlies.sqlitebrowser.org/latest/DB.Browser.for.SQLite-win32.zip

Just extract it and run the .exe - nothing to install (and won't interfere with your current installation)