subject:"\[digikam\] \[Bug 381877\] Digikam start allocating all memory when scans a new collection."

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2019-12-24 Thread bugzilla_noreply

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

   Version Fixed In||7.0.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-12-17 Thread bugzilla_noreply

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

--- Comment #39 from caulier.gil...@gmail.com ---
Following this commit:

https://commits.kde.org/digikam/6a9fd9891a3ff341dc42fe36158cbf0101d513b6

... the approach to fix this problem is under way and new digiKam 5.8.0
pre-release bundles will be compiled tonight to lets a chance to end-users to
give a feedback about this fix before the 5.8.0 official release planed before
Christmas 2017.

The bundles will be available in 2 hours at this url:

https://files.kde.org/digikam/

Please do not waste time to test if this file is always valid for next 5.8.0.

Thanks in advance

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-12-17 Thread Maik Qualmann

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

--- Comment #38 from Maik Qualmann  ---
Git commit 6a9fd9891a3ff341dc42fe36158cbf0101d513b6 by Maik Qualmann.
Committed on 17/12/2017 at 19:20.
Pushed by mqualmann into branch 'master'.

delete threads from memory when they are finished
Related: bug 375317, bug 375035, bug 321784, bug 325712, bug 328732, bug
330227, bug 331912, bug 344661, bug 345395, bug 350549, bug 338249, bug 329651,
bug 329091, bug 387821, bug 381222

M  +2-1NEWS
M  +25   -0libs/database/dbjobs/dbjobsmanager.cpp
M  +35   -0libs/iojobs/iojobsmanager.cpp

https://commits.kde.org/digikam/6a9fd9891a3ff341dc42fe36158cbf0101d513b6

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-29 Thread Simon

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

Simon  changed:

   What|Removed |Added

 CC||freisi...@gmail.com
 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-29 Thread bugzilla_noreply

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

--- Comment #37 from giggi1...@yahoo.com ---
(In reply to caulier.gilles from comment #36)
> Any feedback here ?
> 
> Gilles Caulier

Digikam works again, I've done nothing.
Probably it was a problem with an external lib.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-27 Thread bugzilla_noreply

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

--- Comment #36 from caulier.gil...@gmail.com ---
Any feedback here ?

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-15 Thread bugzilla_noreply

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

--- Comment #35 from caulier.gil...@gmail.com ---
You have a huge memory link about your NVidia video driver :

282,927 bytes in 1 blocks are possibly lost in loss record 47,954 of 47,969
==24333==at 0x4C2DF55: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==24333==by 0x43F4DE92: ??? (in /usr/lib/libGLX_nvidia.so.381.22)
==24333==by 0x454783A0: ??? (in /usr/lib/libnvidia-glcore.so.381.22)

It's about OpenGL layer used... everywhere, as QtAV, OpenCV, Qt...

This is why it's not only relevant of on part of digiKam. The leak is
everywhere.

My tips to confirm :

- Create a VM with virtual box, and install a secondary system inside.
- install digiKam in this VM.
- run and check memory (here is work perfectly)

The VM will emulate OpenGL with an additional layer which will not use the
Nvidia driver directly.

About the original problem, you nivia package from your Linux has a serious
problem. I use also at work exclusively the NVidia cards for the Linux box
(nothing about DK), and i already seen this kind of problem. Updating the
driver or fixing the OpenGL settings can be a solution. There is a huge Nvidia
control panel to tune all the configurations.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-15 Thread bugzilla_noreply

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

--- Comment #34 from giggi1...@yahoo.com ---
(In reply to caulier.gilles from comment #32)
> Go to DK setup/color-management and turn off the first option on top of the
> page.
> 
> Gilles Caulier

The problem has not been solved (with qtav 1.12)

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-15 Thread bugzilla_noreply

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

--- Comment #33 from giggi1...@yahoo.com ---
(In reply to caulier.gilles from comment #32)
> Go to DK setup/color-management and turn off the first option on top of the
> page.
> 
> Gilles Caulier

That's the result.
https://pastebin.com/kH7hx05K

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-15 Thread bugzilla_noreply

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

--- Comment #32 from caulier.gil...@gmail.com ---
Go to DK setup/color-management and turn off the first option on top of the
page.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-15 Thread bugzilla_noreply

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

--- Comment #31 from giggi1...@yahoo.com ---
How do you turn off the ICC color profile?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-15 Thread bugzilla_noreply

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

  Component|Searches|Database-Scan

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-15 Thread bugzilla_noreply

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

--- Comment #30 from caulier.gil...@gmail.com ---
2,874,814 bytes in 59 blocks are still reachable in loss record 42,450 of
42,454
==14781==by 0xE57BA04: cmsOpenIOhandlerFromMem (in
/usr/lib/liblcms2.so.2.0.8)
==14781==by 0xE57D2C4: cmsOpenProfileFromMemTHR (in
/usr/lib/liblcms2.so.2.0.8)
==14781==by 0x5D19CA8: Digikam::IccProfile::open() (in
/usr/lib/libdigikamcore.so.5.6.0)
==14781==by 0x5D24328: Digikam::IccSettings::Private::scanDirectory(QString
const&, QStringList const&, QList*) (in
/usr/lib/libdigikamcore.so.5.6.0)
==14781==
==14781== 2,876,289 bytes in 59 blocks are still reachable in loss record
42,451 of 42,454
==14781==by 0x87AF923: QArrayData::allocate(unsigned long, unsigned long,
unsigned long, QFlags) (in
/usr/lib/libQt5Core.so.5.9.1)
==14781==by 0x87B23C3: QByteArray::resize(int) (in
/usr/lib/libQt5Core.so.5.9.1)
==14781==by 0x88B410D: QIODevice::readAll() (in
/usr/lib/libQt5Core.so.5.9.1)
==14781==by 0x5D1970F: Digikam::IccProfile::data() (in
/usr/lib/libdigikamcore.so.5.6.0)
==14781==by 0x5D19BAF: Digikam::IccProfile::open() (in
/usr/lib/libdigikamcore.so.5.6.0)

This happen when digiKAm scan ICC color profiles from your system. Typically,
you have the color management turned on.

Turn off CM and try again. Perhaps you have corrupted ICC color profile on your
system.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-15 Thread bugzilla_noreply

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

--- Comment #29 from giggi1...@yahoo.com ---
A pair of logs from valgrind
The second one is incomplete.


> valgrind --tool=memcheck --leak-check=full --error-limit=no  digikam

https://pastebin.com/JwvwiNd3

---
---


> valgrind --tool=memcheck --leak-check=full --error-limit=no 
> --show-leak-kinds=all digikam

https://pastebin.com/q88sw263

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-13 Thread bugzilla_noreply

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

--- Comment #28 from nvl...@yahoo.fr ---
Here are some extracts of valgrind outputs.
I don't have more, because I've not reinstalled qtAV 1.12, sorry for that. 

[...]
==1397== 576 bytes in 1 blocks are possibly lost in loss record 46,312 of
49,097
==1397==at 0x4C2DF05: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1397==by 0x40119F1: allocate_dtv (in /usr/lib/ld-2.25.so)
==1397==by 0x401236D: _dl_allocate_tls (in /usr/lib/ld-2.25.so)
==1397==by 0xE333DC9: pthread_create@@GLIBC_2.2.5 (in
/usr/lib/libpthread-2.25.so)
==1397==by 0x879B875: QThread::start(QThread::Priority) (in
/usr/lib/libQt5Core.so.5.9.1)
==1397==by 0x1232DC22:
QtAV::VideoFrameExtractor::VideoFrameExtractor(QObject*) (in
/usr/lib/libQtAV.so.1.12.0)
==1397==by 0x5EF8824: Digikam::VideoThumbnailer::VideoThumbnailer(QObject*)
(in /usr/lib/libdigikamcore.so.5.6.0)
==1397==by 0x5EF9DE4:
Digikam::VideoThumbnailerJob::VideoThumbnailerJob(QObject*) (in
/usr/lib/libdigikamcore.so.5.6.0)
==1397==by 0x5EEAA06:
Digikam::ThumbnailLoadThread::ThumbnailLoadThread(QObject*) (in
/usr/lib/libdigikamcore.so.5.6.0)
==1397==by 0x55A2A3D: ??? (in /usr/lib/libdigikamgui.so.5.6.0)
==1397==by 0x559C53D: ??? (in /usr/lib/libdigikamgui.so.5.6.0)
==1397==by 0x5106204: ??? (in /usr/lib/libdigikamgui.so.5.6.0)
==1397==  
==1397== 576 bytes in 1 blocks are possibly lost in loss record 46,313 of
49,097
==1397==at 0x4C2DF05: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1397==by 0x40119F1: allocate_dtv (in /usr/lib/ld-2.25.so)
==1397==by 0x401236D: _dl_allocate_tls (in /usr/lib/ld-2.25.so)
==1397==by 0xE333DC9: pthread_create@@GLIBC_2.2.5 (in
/usr/lib/libpthread-2.25.so)
==1397==by 0x879B875: QThread::start(QThread::Priority) (in
/usr/lib/libQt5Core.so.5.9.1)
==1397==by 0x13B696B5: QNetworkConfigurationManagerPrivate::initialize()
(in /usr/lib/libQt5Network.so.5.9.1)
==1397==by 0x13B638EC: qNetworkConfigurationManagerPrivate() (in
/usr/lib/libQt5Network.so.5.9.1)
==1397==by 0x13B63986:
QNetworkConfigurationManager::QNetworkConfigurationManager(QObject*) (in
/usr/lib/libQt5Network.so.5.9.1)
==1397==by 0x174C1FA4: ??? (in /usr/lib/libQt5WebKit.so.5.212.0)
==1397==by 0x89A9241: QObject::event(QEvent*) (in
/usr/lib/libQt5Core.so.5.9.1)
==1397==by 0x788746B: QApplicationPrivate::notify_helper(QObject*, QEvent*)
(in /usr/lib/libQt5Widgets.so.5.9.1)
==1397==by 0x788ECF3: QApplication::notify(QObject*, QEvent*) (in
/usr/lib/libQt5Widgets.so.5.9.1)

[...]
==1397== 2,304 bytes in 4 blocks are possibly lost in loss record 48,185 of
49,097
==1397==at 0x4C2DF05: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1397==by 0x40119F1: allocate_dtv (in /usr/lib/ld-2.25.so)
==1397==by 0x401236D: _dl_allocate_tls (in /usr/lib/ld-2.25.so)
==1397==by 0xE333DC9: pthread_create@@GLIBC_2.2.5 (in
/usr/lib/libpthread-2.25.so)
==1397==by 0x450FFF4B: ??? (in /usr/lib/xorg/modules/dri/radeonsi_dri.so)
==1397==by 0x451003BC: ??? (in /usr/lib/xorg/modules/dri/radeonsi_dri.so)
==1397==by 0x454719F3: ??? (in /usr/lib/xorg/modules/dri/radeonsi_dri.so)
==1397==by 0x4552B57E: amdgpu_winsys_create (in
/usr/lib/xorg/modules/dri/radeonsi_dri.so)
==1397==by 0x44E50EDE: ??? (in /usr/lib/xorg/modules/dri/radeonsi_dri.so)
==1397==by 0x4517FEE9: ??? (in /usr/lib/xorg/modules/dri/radeonsi_dri.so)
==1397==by 0x4517BC1F: ??? (in /usr/lib/xorg/modules/dri/radeonsi_dri.so)
==1397==by 0x43B77FA4: ??? (in /usr/lib/libGLX_mesa.so.0.0.0)

[...]
==1397== 4,360 bytes in 1 blocks are possibly lost in loss record 48,482 of
49,097
==1397==at 0x4C2BEEF: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1397==by 0x27BA3F90: ??? (in /usr/lib/libsqlite3.so.0.8.6)
==1397==by 0x27BA3502: sqlite3Malloc (in /usr/lib/libsqlite3.so.0.8.6)
==1397==by 0x27BB1A53: ??? (in /usr/lib/libsqlite3.so.0.8.6)
==1397==by 0x27BB22C5: ??? (in /usr/lib/libsqlite3.so.0.8.6)
==1397==by 0x27BAC9FF: ??? (in /usr/lib/libsqlite3.so.0.8.6)
==1397==by 0x27B41A26: ??? (in /usr/lib/libsqlite3.so.0.8.6)
==1397==by 0x27B46A49: ??? (in /usr/lib/libsqlite3.so.0.8.6)
==1397==by 0x27B48410: sqlite3BtreeMovetoUnpacked (in
/usr/lib/libsqlite3.so.0.8.6)
==1397==by 0x27BD604D: sqlite3VdbeExec (in /usr/lib/libsqlite3.so.0.8.6)
==1397==by 0x27BD7F9E: sqlite3_step (in /usr/lib/libsqlite3.so.0.8.6)
==1397==by 0x5019375C: ??? (in
/usr/lib/qt/plugins/sqldrivers/libqsqlite.so)
==1397==  
==1397== 4,360 bytes in 1 blocks are possibly lost in loss record 48,483 of
49,097
==1397==at 0x4C2BEEF: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1397==by 0x27BA3F90: ??? (in /usr/lib/libsqlite3.so.0.8.6)
==1397==by 0x27BA3502: sqlite3Malloc (in /usr/lib/libsqlite3.so.0.8.6)
==1397==by 0x27BB1A53: ??? (in /usr/lib/libsqlite3.so.0.8.6)
==1397==by

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-12 Thread bugzilla_noreply

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

--- Comment #27 from caulier.gil...@gmail.com ---
Ok, now we will investiguate the memory leak with valgrind. Start digiKam from
a console like this :

valgrind --tool=memcheck --leak-check=full --error-limit=no digikam

This will run DK in Valgrind which will catch the memory corruptions. This slow
down digiKam.

Just report here all the trace from the console until the end of digiKam
session.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-11 Thread bugzilla_noreply

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

--- Comment #26 from giggi1...@yahoo.com ---
(In reply to caulier.gilles from comment #25)
> When you downgrade qtav, ffmpeg packages are also downgraded or it still the
> same for both QtAV versions ?

ffmpeg is the same (ffmpeg 1:3.3.2-1).

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-11 Thread bugzilla_noreply

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

--- Comment #25 from caulier.gil...@gmail.com ---
When you downgrade qtav, ffmpeg packages are also downgraded or it still the
same for both QtAV versions ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-11 Thread bugzilla_noreply

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

--- Comment #24 from giggi1...@yahoo.com ---
(In reply to nvlplx from comment #19)
> The situation is quite similar with mine, described on DK user mailing list
> ("memory leak : valgrind backtrace", from Paulux). 
> If it's related, gdb should show nothing. 
> 
> On my system, downgrading qtAV to version 1.11 fixed the problem
> (workaround).

I confirm!
I've downgraded to qtAV 1.11 (from 1.12) and digikam is still working.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-11 Thread bugzilla_noreply

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

--- Comment #23 from caulier.gil...@gmail.com ---
And if you scan a collection without video files, the problem is not
reproducible ?

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-11 Thread bugzilla_noreply

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

--- Comment #22 from giggi1...@yahoo.com ---
(In reply to caulier.gilles from comment #20)
> QtAV is to handle video files. Do you have any video in your collection
> while scanning which can explain why downgrading QtAv can fix the problem ?

Yes I've a pair of MOV videos.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-11 Thread bugzilla_noreply

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

--- Comment #21 from giggi1...@yahoo.com ---
I've installed digikam on a different PC (with ArchLinux) and it works.
The problems seems related to my installation.

So I must rebuild digikam in debug mode, and I'll do the same job with 
> gdb digikam

?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-11 Thread bugzilla_noreply

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

--- Comment #20 from caulier.gil...@gmail.com ---
QtAV is to handle video files. Do you have any video in your collection while
scanning which can explain why downgrading QtAv can fix the problem ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-11 Thread bugzilla_noreply

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

nvl...@yahoo.fr changed:

   What|Removed |Added

 CC||nvl...@yahoo.fr

--- Comment #19 from nvl...@yahoo.fr ---
The situation is quite similar with mine, described on DK user mailing list
("memory leak : valgrind backtrace", from Paulux). 
If it's related, gdb should show nothing. 

On my system, downgrading qtAV to version 1.11 fixed the problem (workaround).

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-10 Thread Maik Qualmann

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

--- Comment #18 from Maik Qualmann  ---
I understand it correctly, new account and only 2 images? Very strange. Can you
use gdb and look where digikam is after Ctrl-c? Possibly several attempts. The
output of the console is ok.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-09 Thread bugzilla_noreply

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

--- Comment #17 from giggi1...@yahoo.com ---
I've tried with a new user on an empty collection.
And the problem is still here.

I've added two attachment with a screenshot of ksysguard. 

The log:

$ digikam 
digikam.general: AlbumWatch use QFileSystemWatcher
digikam.general: Database Parameters:
   Type: "QSQLITE"
   DB Core Name: "/mnt/disco_d/picture/digikam4.db"
   DB Thumbs Name:   "/mnt/disco_d/picture/thumbnails-digikam.db"
   DB Face Name: "/mnt/disco_d/picture/recognition.db"
   Connect Options:  ""
   Host Name:""
   Host port:-1
   Internal Server:  false
   Internal Server Path: ""
   Internal Server Serv Cmd: ""
   Internal Server Init Cmd: ""
   Username: ""
   Password: ""

digikam.dbengine: Loading SQL code from config file
"/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected:  3  found:  3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version  8
digikam.coredb: Core database: makeUpdates  8  to  8
digikam.database: Creating new Location  "/picture"  uuid 
"volumeid:?uuid=eecebd58cebd19b3"
digikam.database: location for  "/mnt/disco_d/picture"  is available  true
KMemoryInfo: Platform identified :  "LINUX"
KMemoryInfo: TotalRam:  8356839424
digikam.general: Allowing a cache size of 200 MB
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: Thumbs database: have a structure version  "3"
digikam.general: Thumbnails database ready for use
digikam.dimg: ("/usr/share/color/icc")
digikam.general: Does not contain  "Comment"  Namespace
digikam.metaengine: Loading default values 
digikam.dimg: No X.org XICC profile installed for screen  0
digikam.general: Camera XML data: 
"/home/tmpusr/.local/share/digikam/cameras.xml"
digikam.facedb: FaceDB SelectFaceSetting val ret =  0
digikam.facedb: FaceDB SelectFaceSetting val ret =  0
digikam.facedb: Face database: have a structure version  "2"
digikam.facesengine: Face database ready for use
digikam.general: Face PipeLine: add database writer 
digikam.general: Face PipeLine: add faces trainer   
digikam.facesengine: Face database ready for use
digikam.general: Face PipeLine: add database writer 
digikam.general: Face PipeLine: add faces trainer   
libpng warning: iCCP: known incorrect sRGB profile  
libpng warning: iCCP: known incorrect sRGB profile  
digikam.geoiface: "setting backend marble"  
QtAV 1.12.0(Jun 21 2017, 14:33:46)  
Multimedia framework base on Qt and FFmpeg. 
Distributed under the terms of LGPLv2.1 or later.   
Shanghai University->S3 Graphics->Deepin->PPTV, Shanghai, China Copyright (C)
2012-2016 Wang Bin (aka. Lucas Wang) wbse...@gmail.com 
Donate: http://qtav.org/donate.html 
Source: https://github.com/wang-bin/QtAV
Home page: http://qtav.org
digikam.general: AudioOutput backends: ("OpenAL", "Pulse", "null")
digikam.general: Stacked View Mode :  0
digikam.geoiface: "setting backend marble"
digikam.geoiface: "setting backend marble"
digikam.general: "browse_album"
digikam.general: "browse_tag"
digikam.general: "browse_labels"
digikam.general: "browse_date"
digikam.general: "browse_timeline"
digikam.general: "browse_search"
digikam.general: "browse_fuzzysearch"
digikam.general: "browse_gpssearch"
digikam.general: "browse_people"
digikam.widgets: Paths to color scheme :  ("/usr/share/digikam/colorschemes")
digikam.widgets: "Breeze"  ::  ""
digikam.widgets: "Breeze"  ::  ""
QFSFileEngine::open: No file name specified
digikam.dimg: Root lens database dir:  "/usr/share/lensfun"
digikam.dimg: Load lens database file:  "6x6.xml"
digikam.dimg: Load lens database file:  "actioncams.xml"
digikam.dimg: Load lens database file:  "compact-canon.xml"
digikam.dimg: Load lens database file:  "compact-casio.xml"
digikam.dimg: Load lens database file:  "compact-fujifilm.xml"
digikam.dimg: Load lens database file:  "compact-kodak.xml"
digikam.dimg: Load lens database file:  "compact-konica-minolta.xml"
digikam.dimg: Load lens database file:  "compact-leica.xml"
digikam.dimg: Load lens database file:  "compact-nikon.xml"
digikam.dimg: Load lens database file:  "compact-olympus.xml"
digikam.dimg: Load lens database file:  "compact-panasonic.xml"
digikam.dimg: Load lens database file:  "compact-pentax.xml"
digikam.dimg: Load lens database file:  "compact-ricoh.xml"
digikam.dimg: Load

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-09 Thread bugzilla_noreply

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

--- Comment #16 from giggi1...@yahoo.com ---
Created attachment 106521
  --> https://bugs.kde.org/attachment.cgi?id=106521=edit
Memory

What's happen with the memory.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-09 Thread bugzilla_noreply

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

--- Comment #15 from caulier.gil...@gmail.com ---
Ok, now it's clear.

Next stage is to discovering Which king of file create this memory dysfunction
on your computer.

Remember that it's not reproducible here. Can you imagine this kind of
dysfunction for an application running in production this is not acceptable.

So typically, digiKam allocate the memory when it's scan the collection of
image. Can you confirm ? There is no other operation running in background.
Right ?

If yes, use the digiKam appimage, as explained previously in this thread, but
with another account on your system. Typically, a fresh account where you will
import step by step the albums from your collection, to discover which kind of
files mangle the memory.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-09 Thread bugzilla_noreply

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

--- Comment #14 from giggi1...@yahoo.com ---
(In reply to caulier.gilles from comment #13)
> after the appearance of the problem == > which one.
> 
> The new trace is clear : no crash here.
> 
> Do you seen the main GUI appear ? Why do you press CTRL+C ? Let's the
> application to continuos the scan. All is fine until now.
> 
> Gilles Caulier

The splash screen and GUI appear.

I press ctrl+c because digikam start allocating all memory of my PC, and as a
results the system completely stalls.
That's happen with the ArchLinux version an the appimage.

The problem is not a crash, but the continuous allocation of memory (and
generally the consequence is an indirect crash).


Generally I press ctrl+c at 7.5 Gb ...

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-09 Thread bugzilla_noreply

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

--- Comment #13 from caulier.gil...@gmail.com ---
after the appearance of the problem == > which one.

The new trace is clear : no crash here.

Do you seen the main GUI appear ? Why do you press CTRL+C ? Let's the
application to continuos the scan. All is fine until now.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-09 Thread bugzilla_noreply

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

--- Comment #11 from caulier.gil...@gmail.com ---
Ahah. look well the report :

This application failed to start because it could not find or load the Qt
platform plugin "xcb"
in "".

Available platform plugins are: minimal, offscreen, xcb,
wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimalegl, vnc.

^^^ It said that XCB plugin is missing and it said that plugin available XCB is
here.

Excelent.

I'm sur, the XCB Qt plugin is included in AppImage.

But the most important is the first error :

/tmp/.mount_6terHj/usr/bin/digikam.wrapper: riga 121: 19967 Annullato  
(core dump creato) LD_LIBRARY_PATH="" kdialog --caption "" --title "$TITLE"
-yesno "$TEXT"

The AppImage sdk add rules to register the application in desktop menu (it's
optional).

I suspect that dialog used to ask to end user if the application must be
registered in desktop, crash violently.

There is a quick test to validate this error:

1/ AppÎmage in a simple ISO9960 container loaded dynamically in memory and
mounted in temp dir by the kernel.
2/ mount the appimage manually somewhere on you hard drive and edit the script
used to run digiKam without to pass by AppImage SDK:

   * mkdir ./tmpDK
   * mkdir ./DK5
   * sudo mount appimagefile ./tmpDK
   * cp ./tmpDK/* ./DK5 -r
   * edit file ./DK5/AppRun and remplace at en of file "digikam.wrapper $@" by
"digikam $@"

3/ Run ./DK5/AppRun

If it run (and it work here), the problem is with AppImage desktop integration
rules...

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-09 Thread bugzilla_noreply

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

--- Comment #10 from giggi1...@yahoo.com ---
The log from the appimage (up to the ctrl+c):
(The problem is the same ...)

./digikam-5.6.0-01-x86-64.appimage 
-- digiKam AppImage Bundle
-- Use 'help' as CLI argument to know all available options
This application failed to start because it could not find or load the Qt
platform plugin "xcb"
in "".

Available platform plugins are: minimal, offscreen, xcb,
wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimalegl, vnc.

Reinstalling the application may fix this problem.
/tmp/.mount_6terHj/usr/bin/digikam.wrapper: riga 121: 19967 Annullato  
(core dump creato) LD_LIBRARY_PATH="" kdialog --caption "" --title "$TITLE"
-yesno "$TEXT"
This application failed to start because it could not find or load the Qt
platform plugin "xcb"
in "".

Available platform plugins are: minimal, offscreen, xcb,
wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimalegl, vnc.

Reinstalling the application may fix this problem.
/tmp/.mount_6terHj/usr/bin/digikam.wrapper: riga 121: 19971 Annullato  
(core dump creato) LD_LIBRARY_PATH="" kdialog --caption "" --title "$TITLE"
-yesno "$TEXT"
digikam.widgets: Breeze icons ressource file found
digikam.general: AlbumWatch use QFileSystemWatcher
digikam.general: Database Parameters:
   Type: "QSQLITE"
   DB Core Name:
"/run/media/simone/esterno_xfs/data/Pictures/digikam4.db"
   DB Thumbs Name:  
"/run/media/simone/esterno_xfs/data/Pictures/thumbnails-digikam.db"
   DB Face Name:
"/run/media/simone/esterno_xfs/data/Pictures/recognition.db"
   Connect Options:  ""
   Host Name:""
   Host port:-1
   Internal Server:  false
   Internal Server Path: ""
   Internal Server Serv Cmd: ""
   Internal Server Init Cmd: ""
   Username: ""
   Password: ""

digikam.dbengine: Loading SQL code from config file
"/tmp/.mount_6terHj/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected:  3  found:  3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version  8
digikam.coredb: Core database: makeUpdates  8  to  8
digikam.database: Creating new Location  "/data/Pictures"  uuid 
"volumeid:?uuid=83fe5e0a-66fa-42c9-ad66-05f1bee9c0b2"
digikam.database: location for  "/run/media/simone/esterno_xfs/data/Pictures" 
is available  true
KMemoryInfo: Platform identified :  "LINUX"
KMemoryInfo: TotalRam:  8356839424
digikam.general: Allowing a cache size of 200 MB
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: Thumbs database: have a structure version  "3"
digikam.general: Thumbnails database ready for use
digikam.general: Switch to widget style:  "oxygen"
digikam.dimg: ("/usr/share/color/icc")
digikam.dimg: No X.org XICC profile installed for screen  0
digikam.general: Camera XML data:  "/home/sim/.local/share/digikam/cameras.xml"
digikam.facedb: FaceDB SelectFaceSetting val ret =  0
digikam.facedb: FaceDB SelectFaceSetting val ret =  0
digikam.facedb: Face database: have a structure version  "2"
digikam.facesengine: Face database ready for use
digikam.general: Face PipeLine: add database writer
digikam.general: Face PipeLine: add faces trainer
digikam.facesengine: Face database ready for use
digikam.general: Face PipeLine: add database writer
digikam.general: Face PipeLine: add faces trainer
digikam.geoiface: "setting backend marble"
QtAV 1.11.0(Apr 29 2017, 05:27:51)
Multimedia framework base on Qt and FFmpeg.
Distributed under the terms of LGPLv2.1 or later.
Shanghai University->S3 Graphics->Deepin, Shanghai, ChinaCopyright (C)
2012-2016 Wang Bin (aka. Lucas Wang) wbse...@gmail.com
Donate: http://qtav.org/donate.html
Source: https://github.com/wang-bin/QtAV
Home page: http://qtav.org
capi::version: 0.6.0
digikam.general: AudioOutput backends: ("OpenAL", "null")
digikam.general: Stacked View Mode :  0
digikam.geoiface: "setting backend marble"
digikam.geoiface: "setting backend marble"
digikam.general: "browse_album"
digikam.general: "browse_tag"
digikam.general: "browse_labels"
digikam.general: "browse_date"
digikam.general: "browse_timeline"
digikam.general: "browse_search"
digikam.general: "browse_fuzzysearch"
digikam.general: "browse_gpssearch"
digikam.general: "browse_people"
digikam.widgets: Paths to color scheme : 
("/tmp/.mount_6terHj/usr/share/digikam/colorschemes",
"/usr/share/digikam/colorschemes")
digikam.widgets: "Breeze"  ::  ""
digikam.widgets: "DarkRoom"  :: 
"/usr/share/digikam/colorschemes/darkroom.colors"
digikam.widgets: "DarkRoom"  :: 
"/usr/share/digikam/colorschemes/darkroom.colors"
QFSFileEngine::open: No file name specified
digikam.dimg: Root lens database dir:  "/tmp/.mount_6terHj/usr/share/lensfun"
digikam.dimg: Load lens database file:  "6x6.xml"
digikam.dimg: Load lens

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-09 Thread bugzilla_noreply

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

--- Comment #9 from giggi1...@yahoo.com ---
The exiv2 used in Archlinux: 0.25
https://www.archlinux.org/packages/extra/i686/exiv2/

But is not listed in the dependencies of digikam.
https://www.archlinux.org/packages/extra/x86_64/digikam/


Some images form my camera.
https://www.dropbox.com/sh/cg70llotcif22af/AAA6q9kw4vYNvktYTNbeocBRa?dl=0

Where's the beta?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-08 Thread Maik Qualmann

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #8 from Maik Qualmann  ---
Which libexiv2 version do you use, see digiKam component info? Please try the
beta AppImage from www.digikam.org to reproduce the error. Can you share a few
samples from the Olympus camera files?

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-08 Thread bugzilla_noreply

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

--- Comment #7 from giggi1...@yahoo.com ---
The log of digikam up to the ctrl+c

digikam.general: AlbumWatch use QFileSystemWatcher
digikam.general: Database Parameters:
   Type: "QSQLITE"
   DB Core Name:
"/run/media/simone/esterno_xfs/data/Pictures/digikam4.db"
   DB Thumbs Name:  
"/run/media/simone/esterno_xfs/data/Pictures/thumbnails-digikam.db"
   DB Face Name:
"/run/media/simone/esterno_xfs/data/Pictures/recognition.db"
   Connect Options:  ""
   Host Name:""
   Host port:-1
   Internal Server:  false
   Internal Server Path: ""
   Internal Server Serv Cmd: ""
   Internal Server Init Cmd: ""
   Username: ""
   Password: ""

digikam.dbengine: Loading SQL code from config file
"/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected:  3  found:  3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version  8
digikam.coredb: Core database: makeUpdates  8  to  8
digikam.database: Creating new Location  "/data/Pictures"  uuid 
"volumeid:?uuid=83fe5e0a-66fa-42c9-ad66-05f1bee9c0b2"
digikam.database: location for  "/run/media/simone/esterno_xfs/data/Pictures" 
is available  true
KMemoryInfo: Platform identified :  "LINUX"
KMemoryInfo: TotalRam:  8356839424
digikam.general: Allowing a cache size of 200 MB
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: Thumbs database: have a structure version  "3"
digikam.general: Thumbnails database ready for use
digikam.general: Switch to widget style:  "oxygen"
digikam.dimg: ("/usr/share/color/icc")
digikam.dimg: No X.org XICC profile installed for screen  0
digikam.general: Camera XML data:  "/home/sim/.local/share/digikam/cameras.xml"
digikam.facedb: FaceDB SelectFaceSetting val ret =  0
digikam.facedb: FaceDB SelectFaceSetting val ret =  0
digikam.facedb: Face database: have a structure version  "2"
digikam.facesengine: Face database ready for use
digikam.general: Face PipeLine: add database writer
digikam.general: Face PipeLine: add faces trainer
digikam.facesengine: Face database ready for use
digikam.general: Face PipeLine: add database writer
digikam.general: Face PipeLine: add faces trainer
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
digikam.geoiface: "setting backend marble"
QtAV 1.12.0(Jun 21 2017, 14:33:46)
Multimedia framework base on Qt and FFmpeg.
Distributed under the terms of LGPLv2.1 or later.
Shanghai University->S3 Graphics->Deepin->PPTV, Shanghai, China Copyright (C)
2012-2016 Wang Bin (aka. Lucas Wang) wbse...@gmail.com
Donate: http://qtav.org/donate.html
Source: https://github.com/wang-bin/QtAV
Home page: http://qtav.org
digikam.general: AudioOutput backends: ("OpenAL", "Pulse", "null")
digikam.general: Stacked View Mode :  0
digikam.geoiface: "setting backend marble"
digikam.geoiface: "setting backend marble"
digikam.general: "browse_album"
digikam.general: "browse_tag"
digikam.general: "browse_labels"
digikam.general: "browse_date"
digikam.general: "browse_timeline"
digikam.general: "browse_search"
digikam.general: "browse_fuzzysearch"
digikam.general: "browse_gpssearch"
digikam.general: "browse_people"
digikam.widgets: Paths to color scheme :  ("/usr/share/digikam/colorschemes")
digikam.widgets: "Breeze"  ::  ""
digikam.widgets: "DarkRoom"  :: 
"/usr/share/digikam/colorschemes/darkroom.colors"
QFSFileEngine::open: No file name specified
digikam.dimg: Root lens database dir:  "/usr/share/lensfun"
digikam.dimg: Load lens database file:  "6x6.xml"
digikam.dimg: Load lens database file:  "actioncams.xml"
digikam.dimg: Load lens database file:  "compact-canon.xml"
digikam.dimg: Load lens database file:  "compact-casio.xml"
digikam.dimg: Load lens database file:  "compact-fujifilm.xml"
digikam.dimg: Load lens database file:  "compact-kodak.xml"
digikam.dimg: Load lens database file:  "compact-konica-minolta.xml"
digikam.dimg: Load lens database file:  "compact-leica.xml"
digikam.dimg: Load lens database file:  "compact-nikon.xml"
digikam.dimg: Load lens database file:  "compact-olympus.xml"
digikam.dimg: Load lens database file:  "compact-panasonic.xml"
digikam.dimg: Load lens database file:  "compact-pentax.xml"
digikam.dimg: Load lens database file:  "compact-ricoh.xml"
digikam.dimg: Load lens database file:  "compact-samsung.xml"
digikam.dimg: Load lens database file:  "compact-sigma.xml"
digikam.dimg: Load lens database file:  "compact-sony.xml"
digikam.dimg: Load lens database file:  "contax.xml"
digikam.dimg: Load lens database file:  "generic.xml"
digikam.dimg: Load lens database file:  "mil-canon.xml"
digikam.dimg: Load lens database file:  "mil-fujifilm.xml"
digikam.dimg: Load lens database file:  "mil-nikon.xml"
digikam.dimg:

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-08 Thread bugzilla_noreply

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

--- Comment #6 from giggi1...@yahoo.com ---
Created attachment 106510
  --> https://bugs.kde.org/attachment.cgi?id=106510=edit
What's happen

This is the snapshot of the RAM usage caused by digikam.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-02 Thread bugzilla_noreply

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

--- Comment #5 from giggi1...@yahoo.com ---
The log message likes a problem with Qt.
But the time is correlated with digikam.

Strange.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-02 Thread bugzilla_noreply

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

--- Comment #4 from caulier.gil...@gmail.com ---
QXcbConnection: XCB error: sound like a packaging system problem.

Here this kind of freeze are never seen. My collection is huge (more than
200.000 items as RAW, JPG, PNg, TIFF, MPG, MOV, AVI, MKV, etc...)

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-02 Thread bugzilla_noreply

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

--- Comment #3 from giggi1...@yahoo.com ---
Now I've tried to move the new folder outside the collection.
As a result I've obtained a similar freeze.
The system was freezed for a pair of minutes when finished digikam has crashed.

Two suspect entry in journalctl log:
lug 02 09:02:20 sir kwin_x11[1250]: QXcbConnection: XCB error: 3 (BadWindow),
sequence: 15298, resource id: 33560089, major code: 3 (GetWindowAttributes),
minor code: 0
lug 02 09:02:20 sir kwin_x11[1250]: QXcbConnection: XCB error: 9 (BadDrawable),
sequence: 15299, resource id: 33560089, major code: 14 (GetGeometry), minor
code: 0

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-02 Thread bugzilla_noreply

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

--- Comment #2 from giggi1...@yahoo.com ---
The new album is a folder with 125 jpeg images.
The average size of a single is about 7.7 Mb.
The photo has been done with an Olympus Omd em 5 camera.

The total size of the album.
> du Harley\ II/ -h
> 901MHarley II/

And finally the album, and the picture collection, is an external USB drive
formatted in XFS.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-01 Thread bugzilla_noreply

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
Can you share the new album contents, just to try to reproduce the problem here
?

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.

2017-07-01 Thread bugzilla_noreply

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

giggi1...@yahoo.com changed:

   What|Removed |Added

Summary|Digikam start allocating|Digikam start allocating
   |all memory when scan a new  |all memory when scans a new
   |collection. |collection.

-- 
You are receiving this mail because:
You are watching all bug changes.

42 matches

Mail list logo