digiKam freezes when scanning a new collection

[Stuart T Rogers]

Although I do not see long hangs/freezes when digikam scans new 
collections or for new images I do see that in general the process slows 
down digikam so that the gui either is very very slow or even 
non-responsive while the process finishes. In my case the directories 
being scanned contain only image files from my cameras. While the 
scanning of new collections is not used a huge amount the process 
looking for new images in existing collections does slow down the 
initial use of digikam on every start of the program. I am running using 
an AMD quad core processor with 8meg memory running openSUSE Tumbleweed.

Stuart

On 23/01/17 10:01, Simon Frei wrote:
> What makes you think that? This is also an issue when importing a folder
> that only contains image files.
> Pure speculation on my side: To me it seems that there is something
> wrong with priority handling (however that is done). Finding new files,
> which does happen in background, still influences other digikam
> functionalities to the point where the UI freezes. This looks like the
> background process takes all resources and any normal operations have to
> wait, while it should be the other way around: Normal operations (e.g.
> user interaction with GUI) should always get the resources it needs and
> background process whatever resources are left.
>
> On 23/01/17 10:14, Gilles Caulier wrote:
>> I think the problem is the registration in DB of non image files and
>> all hidden files.
>>
>> There is patch in bugzilla to introduce a settings to filter unwanted
>> dirs/files while scanning. It's not yet finalized and need to be
>> review. Look here :
>>
>> https://bugs.kde.org/show_bug.cgi?id=123097
>>
>> Gilles Caulier
>>
>

-- 
Website: http://www.stella-maris.org.uk
or:      http://www.broadstairs.org