[digikam] [Bug 327073] New: Random freezes

[Alphazo]

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

            Bug ID: 327073
           Summary: Random freezes
    Classification: Unclassified
           Product: digikam
           Version: 3.5.0
          Platform: Archlinux Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: [hidden email]
          Reporter: [hidden email]

I just installed ArchLinux on a brand new Intel i7 4770S (Haswell). I have the
exact package versions on the new and old machines but when performing simple
operations such a renaming or moving files, DigiKam would just freeze.

In the meantime I also experienced severe issues on Kdenlive when simply
disabling an effect.
You can see my bug report on Kdenlive bug tracker here:
http://www.kdenlive.org/mantis/view.php?id=3186

I then looked at the trace and found this stuff about lock elision that seems
very (hardware) specific to Haswell CPU. http://lwn.net/Articles/534758/

I looked at the ArchLinux PKGBUILD for the current pre-compiled glibc 2.18-9
and it has the "--enable-lock-elision" switch. I then recompiled glibc 2.18-9
but without support for enable-lock-elision and problem was gone.

I haven't had a chance to play with Digikam again but this might have fixed my
instabilities as well. Is there any lock elision related code in Digikam or is
the lock elision implementation in current glibc buggy when ran on Haswell
processors ?

Reproducible: Sometimes

Steps to Reproduce:
- Moving a small number of files to a different album
- Renaming some files
Actual Results:  
Freeze. I have to to force close the application.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #1 from Gilles Caulier <[hidden email]> ---
It's probably a glibc issue on your computer...

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from Gilles Caulier <[hidden email]> ---
It's not a digiKam relevant issue, but more an in-deep  system problem.

Please fix, update or change your host system and try again...

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[François-Xavier Payet]

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

François-Xavier Payet <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #3 from François-Xavier Payet <[hidden email]> ---
I'm not sure it's not a Digikam issues, as KDEEnLive had the same (apparent)
same problem, and did solve it on their end.

Are you sure the issue can't be related to Digikam?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #4 from Gilles Caulier <[hidden email]> ---
>"and did solve it on their end."

How did solve it exactly ? There is a report to KDenlive bugzilla ?

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Alphazo]

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

--- Comment #5 from Alphazo <[hidden email]> ---
The bug report on Kdenlive found in the opening post gives a link to the
following fix:

http://quickgit.kde.org/?p=kdenlive.git&a=commitdiff&h=d049b327afc02b499266b5c895b13e438490b7c0&o=plain

Once I applied this patch (now included in the latest release) problems were
gone. Now I haven't moved a lot of file lately on DigiKam so I cannot comment
on DigiKam stability with Haswell CPU.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #6 from Gilles Caulier <[hidden email]> ---
The commit from KDenlive sound like a missing mutex to lock about
multi-processing rules.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |Portability

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