[digikam] [Bug 314386] New: Digikam crashes on startup with large collections

[Luke Campagnola]

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

            Bug ID: 314386
           Summary: Digikam crashes on startup with large collections
    Classification: Unclassified
           Product: digikam
           Version: 2.8.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: NOR
         Component: general
          Assignee: [hidden email]
          Reporter: [hidden email]

I have a large collection with ~1000 directories. When I start digikam, I
usually see an error about opening too many files (I reported this bug already:
#314385). To work around that issue, I run ulimit -n 2048 before running
digikam. This seems to fix the previous problem, but reveals a different crash
with this error message: "*** buffer overflow detected ***: digikam
terminated". I will attach a backtrace with more information.



Reproducible: Always

Steps to Reproduce:
1. Start fresh: empty ~/Pictures, remove .kde/share/config/digikamrc
2. Create ~/Pictures with 1000 subdirs:
     for i in {1..1000}; do mkdir ~/Pictures/$i; done
3. Run 'ulimit -n 2048'
4. Start digikam
Actual Results:  
Causes crash. If ~/Pictures contains only 100 subdirectories instead of 1000,
then there is no crash.


gdb session attached.

--
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

[Luke Campagnola]

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

--- Comment #1 from Luke <[hidden email]> ---
Created attachment 76890
  --> https://bugs.kde.org/attachment.cgi?id=76890&action=edit
gdb session

--
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=314386

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |[hidden email]
         Resolution|---                         |WAITINGFORINFO

--- Comment #2 from Gilles Caulier <[hidden email]> ---
In your gdb backtrace, there is no digiKam code. Please try to get a new
backtrace more suitable to hack...

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

[Luke Campagnola]

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

Luke <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WAITINGFORINFO              |INVALID

--- Comment #3 from Luke <[hidden email]> ---
The backtrace is quite reproducible, so I'm not sure how to go about generating
anything different. I presume the call to main() at the very last line comes
from digikam.

Given the relationship of this bug to #314385, perhaps it's best to close this
one at least until the prior bug is resolved (since this might just disappear
with it).

--
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=314386

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|INVALID                     |DUPLICATE
          Component|general                     |Portability

--- Comment #4 from [hidden email] ---


*** This bug has been marked as a duplicate of bug 314385 ***

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