Bug 346205 - digiKam hangs often saving an edited picture back to a network share.
Summary: digiKam hangs often saving an edited picture back to a network share.
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: DImg-Processing (show other bugs)
Version: 4.9.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-15 06:59 UTC by Gerard Dirkse
Modified: 2022-02-04 06:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.5.0


Attachments
Refer to problem report (245.04 KB, image/jpeg)
2015-04-15 07:00 UTC, Gerard Dirkse
Details
Refer to problem report (240.33 KB, image/jpeg)
2015-04-15 07:00 UTC, Gerard Dirkse
Details
Refer to problem report (199.92 KB, image/jpeg)
2015-04-15 07:00 UTC, Gerard Dirkse
Details
Refer to problem report (209.54 KB, image/jpeg)
2015-04-15 07:01 UTC, Gerard Dirkse
Details
Refer to problem report (283.48 KB, image/jpeg)
2015-04-15 07:01 UTC, Gerard Dirkse
Details
Refer to problem report (17.92 KB, text/plain)
2015-04-15 07:01 UTC, Gerard Dirkse
Details
Refer to problem report (180.80 KB, text/plain)
2015-04-15 07:02 UTC, Gerard Dirkse
Details
Refer to problem report (21.34 KB, text/plain)
2015-04-15 07:02 UTC, Gerard Dirkse
Details
Refer to problem report (80.14 KB, text/plain)
2015-04-15 07:02 UTC, Gerard Dirkse
Details
Refer to problem report (180.80 KB, text/plain)
2015-04-15 07:03 UTC, Gerard Dirkse
Details
Refer to problem report (698.80 KB, application/gzip)
2015-04-15 07:04 UTC, Gerard Dirkse
Details
Terminal output 2nd reproduction (18.58 KB, text/plain)
2015-04-15 08:06 UTC, Gerard Dirkse
Details
Kdebug output second reproduction (80.97 KB, text/plain)
2015-04-15 08:06 UTC, Gerard Dirkse
Details
lsof before cancelling out of digikam (685.64 KB, application/gzip)
2015-04-15 08:07 UTC, Gerard Dirkse
Details
lsof after cancelling out of digikam (656.04 KB, application/gzip)
2015-04-15 08:07 UTC, Gerard Dirkse
Details
ps output before (2) and after (3) cancelling out of digikam (14.36 KB, application/gzip)
2015-04-15 08:09 UTC, Gerard Dirkse
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gerard Dirkse 2015-04-15 06:59:04 UTC
Initial detection:

digikambug1.jpeg: shows the image window, where the second picture in the image window has been edited and other processes are hanging and can not be cancelled.

digikambug2.jpeg: shows the directory where the second files is the one edited and contains 0 bytes (so it was corrupted/lost)

digikambug3.jpeg and digikambug4.jpeg: shows what happens if you try to terminate digikam

digikambug5.jpeg: shows that second picture is now lost.



Reproducible: Sometimes

Steps to Reproduce:
1. Edit a picture
2. Sve back to network share
3.

Actual Results:  
digikam hang

Expected Results:  
Digikam coontinues

After having recovered the second picture, problem was reproduced.  Environment is Opensuse 13.2, Digikam 4.9 database is MYSQL on network server, pictures are on a samba server on the network.  Laptop to network connnection is wifi (300mbit, excellent quality).

Digikam was run in a terminal window, terminal output is in termoutput.txt, all required kdebug output is in kdebug.dbg.  When digikam hangs directory looks like digikambug8.jpeg. Various other outputs from ps command in psaxjf-out.txt and psaxms-out.txt, output from lsof is in lsof.txt

My impression is that there is a serialisation problem between the various process/threads, which gets itself into a deadly embrace.  Speed of the save is the inducing factor.  Problem is relatively easy to create, but does not happen all the time (but it does happen often).  A reboot is required to resolve the hang.
Comment 1 Gerard Dirkse 2015-04-15 07:00:14 UTC
Created attachment 92038 [details]
Refer to problem report
Comment 2 Gerard Dirkse 2015-04-15 07:00:33 UTC
Created attachment 92039 [details]
Refer to problem report
Comment 3 Gerard Dirkse 2015-04-15 07:00:48 UTC
Created attachment 92040 [details]
Refer to problem report
Comment 4 Gerard Dirkse 2015-04-15 07:01:02 UTC
Created attachment 92041 [details]
Refer to problem report
Comment 5 Gerard Dirkse 2015-04-15 07:01:18 UTC
Created attachment 92042 [details]
Refer to problem report
Comment 6 Gerard Dirkse 2015-04-15 07:01:54 UTC
Created attachment 92043 [details]
Refer to problem report
Comment 7 Gerard Dirkse 2015-04-15 07:02:09 UTC
Created attachment 92044 [details]
Refer to problem report
Comment 8 Gerard Dirkse 2015-04-15 07:02:25 UTC
Created attachment 92045 [details]
Refer to problem report
Comment 9 Gerard Dirkse 2015-04-15 07:02:38 UTC
Created attachment 92046 [details]
Refer to problem report
Comment 10 Gerard Dirkse 2015-04-15 07:03:08 UTC
Created attachment 92047 [details]
Refer to problem report
Comment 11 Gerard Dirkse 2015-04-15 07:04:14 UTC
Created attachment 92048 [details]
Refer to problem report
Comment 12 Gerard Dirkse 2015-04-15 07:51:05 UTC
Just found out that kdebug.dbg  was corrupted by subsequent run of digikam, will reproduce again
Comment 13 Gerard Dirkse 2015-04-15 08:06:02 UTC
Created attachment 92049 [details]
Terminal output 2nd reproduction
Comment 14 Gerard Dirkse 2015-04-15 08:06:25 UTC
Created attachment 92050 [details]
Kdebug output second reproduction
Comment 15 Gerard Dirkse 2015-04-15 08:07:26 UTC
Created attachment 92051 [details]
lsof before cancelling out of digikam
Comment 16 Gerard Dirkse 2015-04-15 08:07:49 UTC
Created attachment 92052 [details]
lsof after cancelling out of digikam
Comment 17 Gerard Dirkse 2015-04-15 08:09:34 UTC
Created attachment 92053 [details]
ps output before (2) and after (3) cancelling out of digikam
Comment 18 Gerard Dirkse 2015-04-23 13:04:53 UTC
Now using LAN connection problem happens less often, but sometimes still hangs 'writing metadata'  Found out that by using 'lsof' which file it is writing to and seems to hang, then to use 'exiftool' on that file will clear the hang and all other waiting tasks hanging behind it.
Comment 19 Mac 2015-04-23 18:11:23 UTC
Crashed after straightening, cropping an image then tried to save as new image in local directory.
Comment 20 caulier.gilles 2015-08-13 08:02:43 UTC
digiKam 4.12.0 is out.

https://www.digikam.org/node/741

Problem still reproducible ?

Gilles Caulier
Comment 21 Gerard Dirkse 2015-08-13 09:25:47 UTC
Unable to test due to bug 351245.
Comment 22 caulier.gilles 2016-06-30 13:00:05 UTC
Problem still reproducible using last digiKam 5.0.0-beta7 ?

Gilles Caulier
Comment 23 caulier.gilles 2016-07-02 18:44:16 UTC
digiKam 5.0.0 will be released soon.

Please test with this version quickly and give us a fresh feedback.
Comment 24 Gerard Dirkse 2016-07-03 06:44:06 UTC
If I need to get this from GIT and then needs to be compiled is going to take days, if I ever get it done, never compiled a KDE app. Is there a binary download somewhere 64bit Linux ?
Comment 25 caulier.gilles 2016-11-21 16:05:00 UTC
We need feedback with last digiKam AppImage Linux Bundle:

https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier
Comment 26 caulier.gilles 2016-11-26 10:34:13 UTC
This problem still reproducible using digiKam AppImage bundle 5.4.0 pre release
?

It available at this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier
Comment 27 caulier.gilles 2017-04-16 20:08:59 UTC
digiKam 5.5.0 is released officially

https://download.kde.org/stable/digikam/

...and new 5.6.0 pre-release as bundle is available here :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Please check if this problem still reproducible with these versions.

Thanks in advance

Gilles Caulier
Comment 28 caulier.gilles 2017-06-22 21:38:51 UTC
digiKam 5.6.0 is now release and available as bundle for Linux, MacOS and Windows.

Can you check if problem still exists with this version ?

Thanks in advance

Gilles Caulier
Comment 29 caulier.gilles 2017-08-09 15:45:32 UTC
No response since a long time. Closed...