GUI sometimes blocked

[wadouk]

Describe the bug

Sometimes, the GUI doesn't respond anymore and after a while it unlock

Steps to reproduce

Load darktable with a big library

Expected behavior

darktable should be fluid and never block or having a spinner somewhere ?

Logfile | Screenshot | Screencast

When it lock this line is here and wait, seems to lock during 15s each time on startup or even without actions on interface

 0,1746 [sql] /usr/src/debug/darktable/darktable-4.4.2/src/common/film.c:539, function dt_film_set_folder_status(): prepare "INSERT INTO memory.film_folder (id, status) VALUES (?1, ?2)"
16,3648 [dt_get_sysresource_level] switched to 1 as `default'

356.5843 [sql] /usr/src/debug/darktable/darktable-4.4.2/src/common/film.c:539, function dt_film_set_folder_status(): prepare "INSERT INTO memory.film_folder (id, status) VALUES (?1, ?2)"
372.9900 [lighttable] expose took 0.0000 sec

Commit

No response

Where did you obtain darktable from?

distro packaging

darktable version

4.6.0

What OS are you using?

Linux

What is the version of your OS?

Linux laptop 5.15.146-1-MANJARO

Describe your system?

Open darktable with 1.8 To of images, around 60k images.
Files stored on a nas mounted with samba share with a symbolic link to workaround an other bug
ln -ds /run/user/1000/gvfs/smb-share:... ~/nas

If I remove the symbolic link, so no more access to the images, the startup of dt is fast and gui answer is ok

seems to be correlated to storage access speed. some stuff without lock the gui should be better.

Are you using OpenCL GPU in darktable?

None

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

idem in 4.4.2
disable all lua

[ralfbrown]

That looks suspiciously like you are accessing a drive which has spun down to save power and needs to spin up again. Or, since you're accessing over a network, just a dropped packet which requires waiting for a timeout before it gets re-sent.

Unfortunately, the GUI toolkit (Gtk) which darktable uses is single-threaded, so any such pause will freeze the interface. It could be worked around by spawning additional threads to handle database access, but that will be quite complicated....

[wadouk]

Seems a protocol or network stuff on linux with samba : works very well on windows so not a problem of power saving but like the log take time after local database access, doesn't see what is accessed. Instead of rewriting the full part to use threads (that will not fix the real delay stuff) just having a way to investivage what happened so frequently and discuss if it's avoidable. Could be profitable to everyone.

[github-actions]

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

[ralfbrown]

Many places where an operation on many images was blocking the UI now show a spinner or progress bar in master. But that doesn't address the problem of a single SQL call for a single image taking multiple seconds.

[github-actions]

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.