| Summary: | Crash after files moved | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Justin Zane Chudgar <justin> |
| Component: | DImg-FileIO | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, justin |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 6.0.0 | |
| Sentry Crash Report: | |||
|
Description
Justin Zane Chudgar
2011-07-13 00:40:37 UTC
*** This bug has been marked as a duplicate of bug 232792 *** Though this has been marked as a duplicate of 232792, I question that based on further experimentation that I have done. Specifically, I created an ext3 partition and migrated Digikam's sqlite database to that partition. This has DRASTICALLY improved Digikam's performance since sqlite's performance on ext3 is an order of magnitude better than on btrfs as of 2.6.37. This has prevented any crashes or freezes of the UI since I made the change. I therefore assume that the cause of the crash is related to sqlite rather than kipi. No. This is the reason of the crash : [KCrash Handler] #6 QIcon::QIcon (this=0x7fffea9dce40, other=...) at image/qicon.cpp:538 #7 0x00007f4ffc44e414 in QAction::icon (this=<value optimized out>) at kernel/qaction.cpp:737 #8 0x00007f5001663a03 in KIPI::PluginLoader::Info::icon (this=0x3632500) at ../../../../libs/libkipi/libkipi/pluginloader.cpp:191 This is a know problem already fixed in libkipi (from kdegraphics/libs). This is why it's have been marked as duplicated. Your DB speed up problem is fully different. Gilles Caulier *** This bug has been marked as a duplicate of bug 232792 *** Thank you for the explanation. What, if anything, should I do about the issues with sqlite on btrfs? Justin Chudgar | Weed, CA 96094 | 530 921 0738 | http://www.justinzane.com/ On 07/13/2011 01:14 PM, Gilles Caulier wrote: > https://bugs.kde.org/show_bug.cgi?id=277669 > > > Gilles Caulier <caulier.gilles@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution| |DUPLICATE > > > > > --- Comment #3 from Gilles Caulier <caulier gilles gmail com> 2011-07-13 20:14:56 --- > No. This is the reason of the crash : > > [KCrash Handler] > #6 QIcon::QIcon (this=0x7fffea9dce40, other=...) at image/qicon.cpp:538 > #7 0x00007f4ffc44e414 in QAction::icon (this=<value optimized out>) at > kernel/qaction.cpp:737 > #8 0x00007f5001663a03 in KIPI::PluginLoader::Info::icon (this=0x3632500) at > ../../../../libs/libkipi/libkipi/pluginloader.cpp:191 > > This is a know problem already fixed in libkipi (from kdegraphics/libs). This > is why it's have been marked as duplicated. > > Your DB speed up problem is fully different. > > Gilles Caulier > > *** This bug has been marked as a duplicate of bug 232792 *** > I suggest to report it to sqlite bugzilla and to see if this problem already exist. In digiKam we only use sqlite. We don't manage sqlite source code. Another suggestion is to migrate from sqlite to mysql. But i recommend to use 2.0.0 where a lots of fixes have been done. forget 1.x release for that. Gilles Caulier I know that this is a known issue for the btrfs devs and probably sqlite as well. I was just wondering if there should be some sort of warning in the Digikam DB setup dialog about BTRFS as well as NFS/Samba mounts. Though I have not seen the benchmarks on openbenchmarking.org yet, from the btrfs mailing list it seems like there is progress being made so the issue will likely resolve itself within the next couple of kernel releases. Thanks for you time and for the excellent software. Justin Chudgar | Weed, CA 96094 | 530 921 0738 | http://www.justinzane.com/ On 07/13/2011 01:47 PM, Gilles Caulier wrote: > https://bugs.kde.org/show_bug.cgi?id=277669 > > > > > > --- Comment #5 from Gilles Caulier <caulier gilles gmail com> 2011-07-13 20:47:27 --- > I suggest to report it to sqlite bugzilla and to see if this problem already > exist. In digiKam we only use sqlite. We don't manage sqlite source code. > > Another suggestion is to migrate from sqlite to mysql. But i recommend to use > 2.0.0 where a lots of fixes have been done. forget 1.x release for that. > > Gilles Caulier > Problem fixed in 6.0.0 where all tools are now in digiKam core |