| Summary: | Digikam crashes on startup with large collections | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Luke <lcampagn> |
| Component: | Portability-Runtime | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | 2.8.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.1.0 | |
| Sentry Crash Report: | |||
| Attachments: | gdb session | ||
Created attachment 76890 [details]
gdb session
In your gdb backtrace, there is no digiKam code. Please try to get a new backtrace more suitable to hack... Gilles Caulier 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). *** This bug has been marked as a duplicate of bug 314385 *** Fixed with #314385 |
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.