[Digikam-devel] [Bug 200830] 100 % CPU usage without obvious reason

[Marcel Wiesweg]

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


Marcel Wiesweg <marcel.wiesweg at gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marcel.wiesweg at gmx.de




--- Comment #7 from Marcel Wiesweg <marcel wiesweg gmx de>  2009-08-01 15:17:01 ---
Milan:
The different db size maybe because you had image fingerprints generated for
your old db.
To find out the reason of your CPU load you can try profiling with callgrind.
You start digikam under "valgrind --tool=callgrind --instr-atstart=no", prepare
your testcase. From a different console type "callgrind_control -i on" to start
profiling and execute your testcase (slow!). Directly afterwards terminate
digikam with "callgrind_control -k" and you have your callgrind output file
generated.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.