Ok, I think, I file a digikam bug. It is not a TW problem. Should have checked this before... When removing the .psd files from "/my/picture/folder/", digikam detects the change and removes items from its database. Then digikam stops writing messages to the terminal uses 1.3% cpu and stays with 1.971% memory. So, no memory leak any more... Cheers, Michael Am 16.06.19 um 16:29 schrieb Michael Born:

Dear Digikam users.

Is the current digikam v6.1.0 running on your tumbleweed system?

For me, digikam is eating all memory. At about 88% memory usage my system freezes. The mouse only reacts after minutes. The keyboard LEDs do not switch on/off any more. Strangely, no OOM killer kills the digikam process that consumes about 103% cpu until the memory is 88% where the cpu goes to about 50%. I then need to hard reset the computer.

Started in a Konsole, digikam.general is reporting repeatedly: "Detected change, triggering rescan of "/my/picture/folder/" Then, there are some pictures from a Photoshop book with .psd extension that "digikam.dimg.qimage: Can not load"

Some weeks ago digikam was working fine.

I suspect a digikam bug or that I got some digikam components mixed from different repos (had such a problem some years ago) kde:extra or something. How can I check that all digikam components are from just one repo?

Thank you, Michael

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org