[Digikam-devel] [digikam] [Bug 346205] New: Digikam hangs (often) saving an edited picture back to a network share.

[gerard.dirkse at kpnmail.nl]

https://bugs.kde.org/show_bug.cgi?id=346205

            Bug ID: 346205
           Summary: Digikam hangs (often) saving an edited picture back to
                    a network share.
           Product: digikam
           Version: 4.9.0
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: Image Editor
          Assignee: digikam-devel at kde.org
          Reporter: gerard.dirkse at kpnmail.nl

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.