[Bug 265241] New: Improve Startup time of digikam

classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] New: Improve Startup time of digikam

Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241

           Summary: Improve Startup time of digikam
           Product: digikam
           Version: 2.0.0
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: [hidden email]
        ReportedBy: [hidden email]


Version:           2.0.0 (using KDE 4.5.4)
OS:                Linux

Starting digikam takes a long time with large collections (ca 100.000 pictures
on nfs mounted drive) with saying on the console:

digikam(11944)/digikam (core) Digikam::AlbumManager::startScan: KDirWatch
method =  "INotify"

could this be done in background, so it will not take 5 minutes to startup

Reproducible: Always

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Gilles Caulier-4
https://bugs.kde.org/show_bug.cgi?id=265241


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]
          Component|general                     |Database




--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Marcel Wiesweg
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241





--- Comment #1 from Marcel Wiesweg <marcel wiesweg gmx de>  2011-02-03 21:51:20 ---
what happens if you switch off "Scan at Startup" in the setup?

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Bugzilla from rene@brandenburger.lu
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241





--- Comment #2 from  <rene brandenburger lu>  2011-02-04 17:35:31 ---
Created an attachment (id=56860)
 --> (http://bugs.kde.org/attachment.cgi?id=56860)
screenshot of the settings page

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Bugzilla from rene@brandenburger.lu
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241





--- Comment #3 from  <rene brandenburger lu>  2011-02-04 17:37:46 ---
do you mean the "Scan for new items at startup" Setting? That is turned off

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Marcel Wiesweg
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241





--- Comment #4 from Marcel Wiesweg <marcel wiesweg gmx de>  2011-02-04 19:30:51 ---
Then what is it doing at startup? I could have accepted that stat'ing files
over a slow network was slow (even not this slow) but with scanning switched
off?

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Bugzilla from rene@brandenburger.lu
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241





--- Comment #5 from  <rene brandenburger lu>  2011-02-05 19:17:01 ---
well, the logging on the console says:

digikam(14764)/digikam (core)
Digikam::IccSettings::IccSettingsPriv::scanDirectories:
("/usr/share/color/icc") digikam(14764)/digikam (core)
Digikam::AlbumManager::startScan: KDirWatch method =  "INotify"
No location could be retrieved for url KUrl("file://")
digikam(14764)/digikam (core) Digikam::ThumbnailCreator::load: Thumbnail is
null for  ""

and the long time is spent between the "INotify" statement and the No Location
could be retrieved ...

How could I find out what it is doing inbetween there?

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Marcel Wiesweg
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241





--- Comment #6 from Marcel Wiesweg <marcel wiesweg gmx de>  2011-02-05 22:11:57 ---
You could run digikam under gdb in the console, and every minute, interupt with
Ctrl+C and get a backtrace with "bt" (if necessary an all-threads backtrace,
"thr appl all bt") then continue with cont

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Bugzilla from rene@brandenburger.lu
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241





--- Comment #7 from  <rene brandenburger lu>  2011-02-06 02:56:10 ---
OK, here we go:

first one:
Program received signal SIGINT, Interrupt.
0x0012e416 in __kernel_vsyscall ()
(gdb) thr appl all bt

Thread 12 (Thread 0xa5dffb70 (LWP 9085)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x032664dc in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0xafd86b54 in ?? () from /usr/lib/libxine.so.1
#3  0x00000000 in ?? ()

Thread 11 (Thread 0xaa761b70 (LWP 9084)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03740df6 in __poll (fds=0x37d7ff4, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x0380c562 in ?? () from /usr/lib/libpulse.so.0
#3  0x037f8ab9 in pa_mainloop_poll () from /usr/lib/libpulse.so.0
#4  0x037faa73 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#5  0x037fab44 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#6  0x0380c303 in ?? () from /usr/lib/libpulse.so.0
#7  0x049dcbd5 in ?? () from /usr/lib/libpulsecommon-0.9.21.so
#8  0x03261cc9 in start_thread (arg=0xaa761b70) at pthread_create.c:304
#9  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 10 (Thread 0xaaf67b70 (LWP 9083)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03740df6 in __poll (fds=0x37d7ff4, nfds=1, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x045a0a1b in g_poll () from /lib/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#3  0x0459343c in ?? () from /lib/libglib-2.0.so.0
#4  0x04593848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0x03156565 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#6  0x03126609 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/libQtCore.so.4
#7  0x03126a8a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#8  0x03022b7e in QThread::exec() () from /usr/lib/libQtCore.so.4
#9  0xafde881a in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#10 0x03025df9 in ?? () from /usr/lib/libQtCore.so.4
#11 0x03261cc9 in start_thread (arg=0xaaf67b70) at pthread_create.c:304
#12 0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 9 (Thread 0xab768b70 (LWP 9082)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03748371 in select () at ../sysdeps/unix/syscall-template.S:82
#2  0xafda0f1c in xine_usec_sleep () from /usr/lib/libxine.so.1
#3  0x00000000 in ?? ()

Thread 8 (Thread 0xb336db70 (LWP 9081)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03266884 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:236
#2  0xafd74b3f in ?? () from /usr/lib/libxine.so.1
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

---Type <return> to continue, or q <return> to quit---
Thread 7 (Thread 0xb3dc5b70 (LWP 9080)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x032664dc in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0x030269c7 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#3  0x0142d57b in Digikam::ParkingThread::run (this=0x87dbdb0) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/libs/threads/threadmanager.cpp:119
#4  0x03025df9 in ?? () from /usr/lib/libQtCore.so.4
#5  0x03261cc9 in start_thread (arg=0xb3dc5b70) at pthread_create.c:304
#6  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 3 (Thread 0xb45c6b70 (LWP 9076)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x032664dc in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0x030269c7 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#3  0x082a30a2 in Digikam::ScanController::run (this=0x87c7ba8) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/scancontroller.cpp:599
#4  0x03025df9 in ?? () from /usr/lib/libQtCore.so.4
#5  0x03261cc9 in start_thread (arg=0xb45c6b70) at pthread_create.c:304
#6  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xb7474b70 (LWP 9075)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03740df6 in __poll (fds=0x37d7ff4, nfds=1, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x045a0a1b in g_poll () from /lib/libglib-2.0.so.0
#3  0x0459343c in ?? () from /lib/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#4  0x04593ba7 in g_main_loop_run () from /lib/libglib-2.0.so.0
#5  0x057a69c4 in ?? () from /usr/lib/libgio-2.0.so.0
#6  0x045ba48f in ?? () from /lib/libglib-2.0.so.0
#7  0x03261cc9 in start_thread (arg=0xb7474b70) at pthread_create.c:304
#8  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb7882890 (LWP 9068)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x0373d9b3 in ___xstat64 (vers=3, name=0x92c2b50
"/media/Backup/Privat/Bilder/Eigene Bilder/2010/2010-10-12/DSC_8976.JPG",
buf=0x92bc8ac) at ../sysdeps/unix/sysv/linux/xstat64.c:50
#2  0x030fbbe5 in ?? () from /usr/lib/libQtCore.so.4
#3  0x030fecf1 in
QFSFileEngine::fileFlags(QFlags<QAbstractFileEngine::FileFlag>) const () from
/usr/lib/libQtCore.so.4
#4  0x030b38a9 in ?? () from /usr/lib/libQtCore.so.4
#5  0x030b3a8c in QFileInfo::isHidden() const () from /usr/lib/libQtCore.so.4
#6  0x030aba2b in ?? () from /usr/lib/libQtCore.so.4
#7  0x030ac1cd in ?? () from /usr/lib/libQtCore.so.4
#8  0x030accc9 in ?? () from /usr/lib/libQtCore.so.4
#9  0x030ace8a in QDirIterator::QDirIterator(QString const&, QStringList
const&, QFlags<QDir::Filter>, QFlags<QDirIterator::IteratorFlag>) () from
/usr/lib/libQtCore.so.4
#10 0x030a727f in QDir::entryInfoList(QStringList const&, QFlags<QDir::Filter>,
QFlags<QDir::SortFlag>) const () from /usr/lib/libQtCore.so.4
#11 0x030a74af in QDir::entryInfoList(QFlags<QDir::Filter>,
QFlags<QDir::SortFlag>) const () from /usr/lib/libQtCore.so.4
#12 0x02e254ca in ?? () from /usr/lib/libkdecore.so.5
#13 0x02e25548 in ?? () from /usr/lib/libkdecore.so.5
#14 0x02e25548 in ?? () from /usr/lib/libkdecore.so.5
#15 0x02e25e12 in KDirWatch::addDir(QString const&,
QFlags<KDirWatch::WatchMode>) () from /usr/lib/libkdecore.so.5
---Type <return> to continue, or q <return> to quit---
#16 0x081ea0ba in Digikam::AlbumManager::addAlbumRoot (this=0x8634c48,
location=...) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/albummanager.cpp:1207
#17 0x081e9b30 in Digikam::AlbumManager::startScan (this=0x8634c48) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/albummanager.cpp:1134
#18 0x0822eab2 in Digikam::DigikamApp::DigikamApp (this=0x8834018,
__in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/digikamapp.cpp:259
#19 0x0830e119 in main (argc=1, argv=0xbffff3a4) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/main.cpp:188

==========================================================================
second one:


^C
Program received signal SIGINT, Interrupt.
0x0012e416 in __kernel_vsyscall ()
(gdb) thr appl all bt

Thread 12 (Thread 0xa5dffb70 (LWP 9085)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x032664dc in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0xafd86b54 in ?? () from /usr/lib/libxine.so.1
#3  0x00000000 in ?? ()

Thread 11 (Thread 0xaa761b70 (LWP 9084)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03740df6 in __poll (fds=0x37d7ff4, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x0380c562 in ?? () from /usr/lib/libpulse.so.0
#3  0x037f8ab9 in pa_mainloop_poll () from /usr/lib/libpulse.so.0
#4  0x037faa73 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#5  0x037fab44 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#6  0x0380c303 in ?? () from /usr/lib/libpulse.so.0
#7  0x049dcbd5 in ?? () from /usr/lib/libpulsecommon-0.9.21.so
#8  0x03261cc9 in start_thread (arg=0xaa761b70) at pthread_create.c:304
#9  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 10 (Thread 0xaaf67b70 (LWP 9083)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03740df6 in __poll (fds=0x37d7ff4, nfds=1, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x045a0a1b in g_poll () from /lib/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#3  0x0459343c in ?? () from /lib/libglib-2.0.so.0
#4  0x04593848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0x03156565 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#6  0x03126609 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/libQtCore.so.4
#7  0x03126a8a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#8  0x03022b7e in QThread::exec() () from /usr/lib/libQtCore.so.4
#9  0xafde881a in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#10 0x03025df9 in ?? () from /usr/lib/libQtCore.so.4
#11 0x03261cc9 in start_thread (arg=0xaaf67b70) at pthread_create.c:304
#12 0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 9 (Thread 0xab768b70 (LWP 9082)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03748371 in select () at ../sysdeps/unix/syscall-template.S:82
#2  0xafda0f1c in xine_usec_sleep () from /usr/lib/libxine.so.1
#3  0x00000000 in ?? ()

Thread 8 (Thread 0xb336db70 (LWP 9081)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03266884 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:236
#2  0xafd74b3f in ?? () from /usr/lib/libxine.so.1
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

---Type <return> to continue, or q <return> to quit---
Thread 7 (Thread 0xb3dc5b70 (LWP 9080)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x032664dc in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0x030269c7 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#3  0x0142d57b in Digikam::ParkingThread::run (this=0x87dbdb0) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/libs/threads/threadmanager.cpp:119
#4  0x03025df9 in ?? () from /usr/lib/libQtCore.so.4
#5  0x03261cc9 in start_thread (arg=0xb3dc5b70) at pthread_create.c:304
#6  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 3 (Thread 0xb45c6b70 (LWP 9076)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x032664dc in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0x030269c7 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#3  0x082a30a2 in Digikam::ScanController::run (this=0x87c7ba8) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/scancontroller.cpp:599
#4  0x03025df9 in ?? () from /usr/lib/libQtCore.so.4
#5  0x03261cc9 in start_thread (arg=0xb45c6b70) at pthread_create.c:304
#6  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xb7474b70 (LWP 9075)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03740df6 in __poll (fds=0x37d7ff4, nfds=1, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x045a0a1b in g_poll () from /lib/libglib-2.0.so.0
#3  0x0459343c in ?? () from /lib/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#4  0x04593ba7 in g_main_loop_run () from /lib/libglib-2.0.so.0
#5  0x057a69c4 in ?? () from /usr/lib/libgio-2.0.so.0
#6  0x045ba48f in ?? () from /lib/libglib-2.0.so.0
#7  0x03261cc9 in start_thread (arg=0xb7474b70) at pthread_create.c:304
#8  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb7882890 (LWP 9068)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03714202 in __getdents64 (fd=848, buf=0x944cc68 "\025\302\373\006",
nbytes=32768) at ../sysdeps/unix/sysv/linux/getdents.c:156
#2  0x03714565 in __readdir64_r (dirp=0x944cc50, entry=0x936aed0,
result=0x93414c4) at ../sysdeps/unix/readdir_r.c:64
#3  0x030ff8c8 in ?? () from /usr/lib/libQtCore.so.4
#4  0x030ffb5b in ?? () from /usr/lib/libQtCore.so.4
#5  0x030ac0e5 in ?? () from /usr/lib/libQtCore.so.4
#6  0x030accc9 in ?? () from /usr/lib/libQtCore.so.4
#7  0x030ace8a in QDirIterator::QDirIterator(QString const&, QStringList
const&, QFlags<QDir::Filter>, QFlags<QDirIterator::IteratorFlag>) () from
/usr/lib/libQtCore.so.4
#8  0x030a727f in QDir::entryInfoList(QStringList const&, QFlags<QDir::Filter>,
QFlags<QDir::SortFlag>) const () from /usr/lib/libQtCore.so.4
#9  0x030a74af in QDir::entryInfoList(QFlags<QDir::Filter>,
QFlags<QDir::SortFlag>) const () from /usr/lib/libQtCore.so.4
#10 0x02e254ca in ?? () from /usr/lib/libkdecore.so.5
#11 0x02e25548 in ?? () from /usr/lib/libkdecore.so.5
#12 0x02e25548 in ?? () from /usr/lib/libkdecore.so.5
#13 0x02e25548 in ?? () from /usr/lib/libkdecore.so.5
#14 0x02e25e12 in KDirWatch::addDir(QString const&,
QFlags<KDirWatch::WatchMode>) () from /usr/lib/libkdecore.so.5
#15 0x081ea0ba in Digikam::AlbumManager::addAlbumRoot (this=0x8634c48,
location=...) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/albummanager.cpp:1207
---Type <return> to continue, or q <return> to quit---
#16 0x081e9b30 in Digikam::AlbumManager::startScan (this=0x8634c48) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/albummanager.cpp:1134
#17 0x0822eab2 in Digikam::DigikamApp::DigikamApp (this=0x8834018,
__in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/digikamapp.cpp:259
#18 0x0830e119 in main (argc=1, argv=0xbffff3a4) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/main.cpp:188
(gdb)

==========================================================================
a third one:


^C
Program received signal SIGINT, Interrupt.
0x0012e416 in __kernel_vsyscall ()
(gdb) thr appl all bt

Thread 12 (Thread 0xa5dffb70 (LWP 9085)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x032664dc in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0xafd86b54 in ?? () from /usr/lib/libxine.so.1
#3  0x00000000 in ?? ()

Thread 11 (Thread 0xaa761b70 (LWP 9084)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03740df6 in __poll (fds=0x37d7ff4, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x0380c562 in ?? () from /usr/lib/libpulse.so.0
#3  0x037f8ab9 in pa_mainloop_poll () from /usr/lib/libpulse.so.0
#4  0x037faa73 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#5  0x037fab44 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#6  0x0380c303 in ?? () from /usr/lib/libpulse.so.0
#7  0x049dcbd5 in ?? () from /usr/lib/libpulsecommon-0.9.21.so
#8  0x03261cc9 in start_thread (arg=0xaa761b70) at pthread_create.c:304
#9  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 10 (Thread 0xaaf67b70 (LWP 9083)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03740df6 in __poll (fds=0x37d7ff4, nfds=1, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x045a0a1b in g_poll () from /lib/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#3  0x0459343c in ?? () from /lib/libglib-2.0.so.0
#4  0x04593848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0x03156565 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#6  0x03126609 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/libQtCore.so.4
#7  0x03126a8a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#8  0x03022b7e in QThread::exec() () from /usr/lib/libQtCore.so.4
#9  0xafde881a in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#10 0x03025df9 in ?? () from /usr/lib/libQtCore.so.4
#11 0x03261cc9 in start_thread (arg=0xaaf67b70) at pthread_create.c:304
#12 0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 9 (Thread 0xab768b70 (LWP 9082)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03748371 in select () at ../sysdeps/unix/syscall-template.S:82
#2  0xafda0f1c in xine_usec_sleep () from /usr/lib/libxine.so.1
#3  0x00000000 in ?? ()

Thread 8 (Thread 0xb336db70 (LWP 9081)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03266884 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:236
#2  0xafd74b3f in ?? () from /usr/lib/libxine.so.1
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

---Type <return> to continue, or q <return> to quit---
Thread 7 (Thread 0xb3dc5b70 (LWP 9080)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x032664dc in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0x030269c7 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#3  0x0142d57b in Digikam::ParkingThread::run (this=0x87dbdb0) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/libs/threads/threadmanager.cpp:119
#4  0x03025df9 in ?? () from /usr/lib/libQtCore.so.4
#5  0x03261cc9 in start_thread (arg=0xb3dc5b70) at pthread_create.c:304
#6  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 3 (Thread 0xb45c6b70 (LWP 9076)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x032664dc in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0x030269c7 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#3  0x082a30a2 in Digikam::ScanController::run (this=0x87c7ba8) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/scancontroller.cpp:599
#4  0x03025df9 in ?? () from /usr/lib/libQtCore.so.4
#5  0x03261cc9 in start_thread (arg=0xb45c6b70) at pthread_create.c:304
#6  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xb7474b70 (LWP 9075)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03740df6 in __poll (fds=0x37d7ff4, nfds=1, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x045a0a1b in g_poll () from /lib/libglib-2.0.so.0
#3  0x0459343c in ?? () from /lib/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#4  0x04593ba7 in g_main_loop_run () from /lib/libglib-2.0.so.0
#5  0x057a69c4 in ?? () from /usr/lib/libgio-2.0.so.0
#6  0x045ba48f in ?? () from /lib/libglib-2.0.so.0
#7  0x03261cc9 in start_thread (arg=0xb7474b70) at pthread_create.c:304
#8  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb7882890 (LWP 9068)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03714202 in __getdents64 (fd=240, buf=0x94bd780 "\361N\352\006",
nbytes=32768) at ../sysdeps/unix/sysv/linux/getdents.c:156
#2  0x03714565 in __readdir64_r (dirp=0x94bd768, entry=0x94bae38,
result=0x8f8e1f4) at ../sysdeps/unix/readdir_r.c:64
#3  0x030ff8c8 in ?? () from /usr/lib/libQtCore.so.4
#4  0x030ffb5b in ?? () from /usr/lib/libQtCore.so.4
#5  0x030ac0e5 in ?? () from /usr/lib/libQtCore.so.4
#6  0x030accc9 in ?? () from /usr/lib/libQtCore.so.4
#7  0x030ace8a in QDirIterator::QDirIterator(QString const&, QStringList
const&, QFlags<QDir::Filter>, QFlags<QDirIterator::IteratorFlag>) () from
/usr/lib/libQtCore.so.4
#8  0x030a727f in QDir::entryInfoList(QStringList const&, QFlags<QDir::Filter>,
QFlags<QDir::SortFlag>) const () from /usr/lib/libQtCore.so.4
#9  0x030a74af in QDir::entryInfoList(QFlags<QDir::Filter>,
QFlags<QDir::SortFlag>) const () from /usr/lib/libQtCore.so.4
#10 0x02e254ca in ?? () from /usr/lib/libkdecore.so.5
#11 0x02e25548 in ?? () from /usr/lib/libkdecore.so.5
#12 0x02e25548 in ?? () from /usr/lib/libkdecore.so.5
#13 0x02e25548 in ?? () from /usr/lib/libkdecore.so.5
#14 0x02e25548 in ?? () from /usr/lib/libkdecore.so.5
#15 0x02e25e12 in KDirWatch::addDir(QString const&,
QFlags<KDirWatch::WatchMode>) () from /usr/lib/libkdecore.so.5
---Type <return> to continue, or q <return> to quit---
#16 0x081ea0ba in Digikam::AlbumManager::addAlbumRoot (this=0x8634c48,
location=...) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/albummanager.cpp:1207
#17 0x081e9b30 in Digikam::AlbumManager::startScan (this=0x8634c48) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/albummanager.cpp:1134
#18 0x0822eab2 in Digikam::DigikamApp::DigikamApp (this=0x8834018,
__in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/digikamapp.cpp:259
#19 0x0830e119 in main (argc=1, argv=0xbffff3a4) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/main.cpp:188

==========================================================================
and a last one

^C
Program received signal SIGINT, Interrupt.
0x0012e416 in __kernel_vsyscall ()
(gdb) thr appl all bt

Thread 12 (Thread 0xa5dffb70 (LWP 9085)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x032664dc in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0xafd86b54 in ?? () from /usr/lib/libxine.so.1
#3  0x00000000 in ?? ()

Thread 11 (Thread 0xaa761b70 (LWP 9084)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03740df6 in __poll (fds=0x37d7ff4, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x0380c562 in ?? () from /usr/lib/libpulse.so.0
#3  0x037f8ab9 in pa_mainloop_poll () from /usr/lib/libpulse.so.0
#4  0x037faa73 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#5  0x037fab44 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#6  0x0380c303 in ?? () from /usr/lib/libpulse.so.0
#7  0x049dcbd5 in ?? () from /usr/lib/libpulsecommon-0.9.21.so
#8  0x03261cc9 in start_thread (arg=0xaa761b70) at pthread_create.c:304
#9  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 10 (Thread 0xaaf67b70 (LWP 9083)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03740df6 in __poll (fds=0x37d7ff4, nfds=1, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x045a0a1b in g_poll () from /lib/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#3  0x0459343c in ?? () from /lib/libglib-2.0.so.0
#4  0x04593848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0x03156565 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#6  0x03126609 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/libQtCore.so.4
#7  0x03126a8a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#8  0x03022b7e in QThread::exec() () from /usr/lib/libQtCore.so.4
#9  0xafde881a in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#10 0x03025df9 in ?? () from /usr/lib/libQtCore.so.4
#11 0x03261cc9 in start_thread (arg=0xaaf67b70) at pthread_create.c:304
#12 0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 9 (Thread 0xab768b70 (LWP 9082)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03748371 in select () at ../sysdeps/unix/syscall-template.S:82
#2  0xafda0f1c in xine_usec_sleep () from /usr/lib/libxine.so.1
#3  0x00000000 in ?? ()

Thread 8 (Thread 0xb336db70 (LWP 9081)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03266884 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:236
#2  0xafd74b3f in ?? () from /usr/lib/libxine.so.1
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

---Type <return> to continue, or q <return> to quit---
Thread 7 (Thread 0xb3dc5b70 (LWP 9080)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x032664dc in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0x030269c7 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#3  0x0142d57b in Digikam::ParkingThread::run (this=0x87dbdb0) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/libs/threads/threadmanager.cpp:119
#4  0x03025df9 in ?? () from /usr/lib/libQtCore.so.4
#5  0x03261cc9 in start_thread (arg=0xb3dc5b70) at pthread_create.c:304
#6  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 3 (Thread 0xb45c6b70 (LWP 9076)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x032664dc in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0x030269c7 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#3  0x082a30a2 in Digikam::ScanController::run (this=0x87c7ba8) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/scancontroller.cpp:599
#4  0x03025df9 in ?? () from /usr/lib/libQtCore.so.4
#5  0x03261cc9 in start_thread (arg=0xb45c6b70) at pthread_create.c:304
#6  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xb7474b70 (LWP 9075)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x03740df6 in __poll (fds=0x37d7ff4, nfds=1, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x045a0a1b in g_poll () from /lib/libglib-2.0.so.0
#3  0x0459343c in ?? () from /lib/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#4  0x04593ba7 in g_main_loop_run () from /lib/libglib-2.0.so.0
#5  0x057a69c4 in ?? () from /usr/lib/libgio-2.0.so.0
#6  0x045ba48f in ?? () from /lib/libglib-2.0.so.0
#7  0x03261cc9 in start_thread (arg=0xb7474b70) at pthread_create.c:304
#8  0x0374f69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb7882890 (LWP 9068)):
#0  0x0012e416 in __kernel_vsyscall ()
#1  0x0373e066 in statfs () at ../sysdeps/unix/syscall-template.S:82
#2  0x03719b31 in posix_pathconf (file=0x0, name=3) at
../sysdeps/posix/pathconf.c:73
#3  __pathconf (file=0x0, name=3) at ../sysdeps/unix/sysv/linux/pathconf.c:55
#4  0x030ffaf1 in ?? () from /usr/lib/libQtCore.so.4
#5  0x030ac0e5 in ?? () from /usr/lib/libQtCore.so.4
#6  0x030accc9 in ?? () from /usr/lib/libQtCore.so.4
#7  0x030ace8a in QDirIterator::QDirIterator(QString const&, QStringList
const&, QFlags<QDir::Filter>, QFlags<QDirIterator::IteratorFlag>) () from
/usr/lib/libQtCore.so.4
#8  0x030a727f in QDir::entryInfoList(QStringList const&, QFlags<QDir::Filter>,
QFlags<QDir::SortFlag>) const () from /usr/lib/libQtCore.so.4
#9  0x030a74af in QDir::entryInfoList(QFlags<QDir::Filter>,
QFlags<QDir::SortFlag>) const () from /usr/lib/libQtCore.so.4
#10 0x02e254ca in ?? () from /usr/lib/libkdecore.so.5
#11 0x02e25548 in ?? () from /usr/lib/libkdecore.so.5
#12 0x02e25548 in ?? () from /usr/lib/libkdecore.so.5
#13 0x02e25548 in ?? () from /usr/lib/libkdecore.so.5
#14 0x02e25548 in ?? () from /usr/lib/libkdecore.so.5
#15 0x02e25548 in ?? () from /usr/lib/libkdecore.so.5
---Type <return> to continue, or q <return> to quit---
#16 0x02e25e12 in KDirWatch::addDir(QString const&,
QFlags<KDirWatch::WatchMode>) () from /usr/lib/libkdecore.so.5
#17 0x081ea0ba in Digikam::AlbumManager::addAlbumRoot (this=0x8634c48,
location=...) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/albummanager.cpp:1207
#18 0x081e9b30 in Digikam::AlbumManager::startScan (this=0x8634c48) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/albummanager.cpp:1134
#19 0x0822eab2 in Digikam::DigikamApp::DigikamApp (this=0x8834018,
__in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/digikamapp.cpp:259
#20 0x0830e119 in main (argc=1, argv=0xbffff3a4) at
/home/xxx/Documents/exchange/Development/digikam-2.0/digikam/digikam/core/digikam/main.cpp:188
(gdb)



if you need more information, let me know

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Marcel Wiesweg
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241





--- Comment #8 from Marcel Wiesweg <marcel wiesweg gmx de>  2011-02-06 16:36:17 ---
All four are sitting inside KDirWatch:

#16 0x02e25e12 in KDirWatch::addDir(QString const&,
QFlags<KDirWatch::WatchMode>) () from /usr/lib/libkdecore.so.5

so it seems adding a KDirWatch on a NFS directory either hits a bug, or a
worst-case scenario in kdelibs.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Marcel Wiesweg
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241





--- Comment #9 from Marcel Wiesweg <marcel wiesweg gmx de>  2011-02-10 22:10:43 ---
One more question: If you execute "find <path to your collection>", or let
digikam do its collection scan at startup, does it also take 5 minutes?

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Bugzilla from rene@brandenburger.lu
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241





--- Comment #10 from  <rene brandenburger lu>  2011-04-07 23:34:08 ---
find <path_to_my_collection> takes about 4 minutes ...

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Marcel Wiesweg
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241





--- Comment #11 from Marcel Wiesweg <marcel wiesweg gmx de>  2011-04-09 15:38:38 ---
Then NFS is the problem - on a local disk, running find on a directory with
35000 images, with dropped Linux caches, takes about 3 seconds.
I once though about doing the full scan in the background, but even that will
not help if only listing the directory takes enormous time.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Bugzilla from rene@brandenburger.lu
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241





--- Comment #12 from  <rene brandenburger lu>  2011-05-21 19:03:51 ---
listing the directory itself is not so timeconsuming, but scanning the complete
folder structure is taking so long, the collection is organized
<path_to_my_collection>/yyyy/yyyy-mm-dd/<photos> - so doing the fullscan in
background would dramatically reduce startup time

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Gilles Caulier-4
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241





--- Comment #13 from Gilles Caulier <caulier gilles gmail com>  2011-12-15 09:44:11 ---
Rene,

This file still valid using digiKam 2.4 ?

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Bugzilla from shaddowy2@yahoo.de
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241


[hidden email] changed:

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




--- Comment #14 from  <shaddowy2 yahoo de>  2011-12-16 13:48:32 ---
I think I had the same problem. The find command for my picture folder takes
less then one minute, while starting Digikam takes five minutes when the search
for new pictures is enabled. My collection includes only 12k pictures, I don't
think its that big.
When I disable the lookup for new pictures at the start Digikam 2.4.1 starts
very fast now. Great! So I think it's related to Ecryptfs, as my Ext4 partition
is encrypted with Ecryptfs.
For me that bug is fixed.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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
Reply | Threaded
Open this post in threaded view
|

[Bug 265241] Improve Startup time of digikam

Axel Krebs
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241

Axel Krebs <[hidden email]> changed:

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

--- Comment #15 from Axel Krebs <[hidden email]> ---
Hello,

I can confirm much better starting times.
My version ist DigiKam 2.6.

There are weird crashes, however. Some of the re-starting tims as follows:
Ceash        re-opening         time                    loading message
06:53:44    06:50:23            00:03:21             00:00:02
08:07:51    08:10:17            00:02:26             00:00:02
07:33:40    07:35:26            00:01:46             00:00:02
08:13:04    08:14:03            00:00:59             00:00:02
09:34:13    09:35:50            00:01:37             00:00:02
09:55:20    09:58:36            00:03:16             00:00:02

So, in average, the re-opening-time after crash ist quite shorter than before.

The misleading DigiKam-message is:

"digikam                  "        
"Process is done      "        
"Duration 00:00:02"            

So it looks like a programmed (=fixed!!) number "00:00:02" , rather then a
confirmed measured one, which could be a indicator for something....

Therefore I suggest to deal this number seriousloy and correct- or leave it out


Axel

--
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
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 265241] SCAN : Improve Startup time of digikam

Gilles Caulier-4
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Improve Startup time of     |SCAN : Improve Startup time
                   |digikam                     |of digikam

--- Comment #16 from Gilles Caulier <[hidden email]> ---
This entry still valid using last digiKam 4.2.0 ?

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
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 265241] SCAN : Improve Startup time of digikam with remote collections

Gilles Caulier-4
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|SCAN : Improve Startup time |SCAN : Improve Startup time
                   |of digikam                  |of digikam with remote
                   |                            |collections

--
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
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 265241] SCAN : improve digiKam startup time with remote collections

Gilles Caulier-4
In reply to this post by Bugzilla from rene@brandenburger.lu
https://bugs.kde.org/show_bug.cgi?id=265241

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|SCAN : Improve Startup time |SCAN : improve digiKam
                   |of digikam with remote      |startup time with remote
                   |collections                 |collections

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