Bug 345942

Summary:	Leak of memory when color autocorrection used on all processor cores
Product:	[Applications] digikam	Reporter:	Konstantin <Shtirliz.Shtepa>
Component:	Plugin-Bqm-AutoCorrection	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	crash	CC:	caulier.gilles
Priority:	NOR
Version:	4.8.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:	4.10.0
Sentry Crash Report:

Description Konstantin 2015-04-07 07:53:22 UTC

Using color autocorrection on all processor cores in Batch Queue Manager makes Digikam fill all available memory and then crash.

Another Batch Queue Manager function(turn photos to black and white) worked fine on all cores.
Color autocorrection works fine too on single core, when "work on all cores" feature disabled.

Reproducible: Always

Steps to Reproduce:
1. Select photos in Digikam(I selected 196) and click Batch Queue Manager
2. Select Batch Queue Manager to work on all processor cores
3. Select color autocorrection for photos
4. Click Start

Actual Results:  
All memory would be filled and then application crashed.

Expected Results:  
All memory shouldn't be filled and application should work normally.

Opensuse 13.2 x64 
Linux 3.16.7
KDE 4.14.6

Comment 1 caulier.gilles 2015-04-07 08:00:55 UTC

This is not a memory leak. 

A limitation must be add to ajust core to use depending of memory available.

Gilles Caulier

Comment 2 Konstantin 2015-04-08 06:55:24 UTC

(In reply to Gilles Caulier from comment #1)
> This is not a memory leak. 
> A limitation must be add to ajust core to use depending of memory available.
> Gilles Caulier

Maybe. But it used too much memory for operations. And with each operation more and more until it crashed. It's typical behavior for memory leak.

But then again, yesterday after i report there appeared new buld on repository. I installed it now and can't see that buggish behavior anymore. Now on exact same operations memory used like it should(less that 2 GB, when yesterday it pass over 10 GB and crashed) and all works fine(except strange long freezes of all digikam UI after queue operations, but I think it not queue manager issue).
So maybe it was just broken build. I would test it more in next few days and then close this ticket if all goes normally.

Comment 3 Konstantin 2015-04-09 04:31:17 UTC

Updated to 4.9.0
No trace of this bug too. =)
Ticket Closed.