[Digikam-devel] [digikam] [Bug 351658] Prevent to fill whole memory when all CPU cores are used to process Maintenance tools

[Bizy]

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

--- Comment #8 from Bizy <koen.bizy at gmail.com> ---
(In reply to Gilles Caulier from comment #7)
> Downgrading digiKam will certainly downgrade other components, as Exiv2
> library. With previous 0.24.0 release a lots of bugs have been introduced.
> Using previous version do not have these problems. Writing metadata to image
> use Exiv2 a lots.
> 
> Exiv2 0.25.0 fix the problem. This version must be used with digiKam
> 4.12.0...
> 
> Note : your problem sound like completely different than report title, but
> my title changes are true. If you run maintenance tools with all CPU core,
> there is no check to see how many memory is available to process, and all is
> filled. Here with 16 or 32 GB, there are no problem to run 8 threads with a
> i7 cpu, but with 8 or 4 Gb, it's completely different.
> 
> Gilles Caulier

Thanks, Gilles, for your comment!

1) Regarding Exiv:  can you tell me how to do this upgrade step by step (or
send me a link)?  Of course, I know about this problem, it's been reported
often.  But then again:  I didn't find any clear (meaning:  clear to me)
instructions on how to upgrade, as it got too technical.  I tried (or actually
did) upgrade exiv with the terminal, but I wonder if that's enough.  There seem
to be isues with older parts that need to be removed in another way... That's
where the too technical part starts...

2)  Regarding the title:  fine to me!  As long as it's clear enough for you
guys to idenitfy the problem... ;-)
Seems that I have to regret I didn't order more memory then? :-(
But I read about the 'same' (at least regarding memory leak) problem for
someone with 32GB of memory... (same behaviour, gradually using it all, and
then crashing or disappearing...)
(tried to google it, but can't find it for now)

-- 
You are receiving this mail because:
You are the assignee for the bug.