[Digikam-users] kipi picasa export freeze on 1.9

Julien T julien.t43 at gmail.com
Fri Jun 24 09:17:35 BST 2011


Hello,

Since beginning of June, when uploading pictures with Picasa kipi
plugins, I have some freeze after x pictures (usually between 4 and 8
on 10 to 60 photos upload)
I can move Windows, sometimes close button works, sometimes not but
there is no more cpu / memory activity from digikam.

That's with 1.9.0. I just updated to 2.0 so I will see if I can reproduce this.

I try to debug it with gdb but not easy as there is no
backtrace/crash. it's a freeze.
But I see a lot of messages:

>>>
Bound values:  (QVariant(QString, "20110612_002042--P6120096.JPG") ,
QVariant(int, 1) ,  QVariant(QString, "/20110612") )
digikam(11843)/digikam (core)
Digikam::DatabaseCoreBackendPrivate::debugOutputFailedQuery: Failure
executing query:
 "SELECT Images.id, Albums.id  FROM Images INNER JOIN Albums   ON
Images.album=Albums.id  WHERE name=? AND albumRoot=? AND
relativePath=?;"
Error messages: "database is locked Unable to fetch row" 5 1 "database
is locked" "Unable to fetch row" QSqlError(-1, "", "")
<<<

or

>>>
digikam(12625)/digikam (core)
Digikam::DatabaseCoreBackendPrivate::debugOutputFailedQuery: Failure
executing query:
 "SELECT id, type, language, author, date, comment FROM ImageComments
WHERE imageid=?;"
Error messages: "database is locked Unable to fetch row" 5 1 "database
is locked" "Unable to fetch row" QSqlError(-1, "", "")
Bound values:  (QVariant(qlonglong, 75264) )
digikam(12625)/digikam (core)
Digikam::DatabaseCoreBackendPrivate::checkRetrySQLiteLockError:
Detected locked database file. There is an active transaction.
<<<

Problem is, from GUI perspective, the only thing digikam is doing is
"export to picasa" (the export window is modal - can't access digikam
main window while active). So don't understand what operation is
locking DB.

I checked http://www.sqlite.org/lockingv3.html quickly but did not see
a way to identify the culprit request.
And normally, it seems there is a 5 seconds timeout for all request.

Any hints to solve this ?


Thanks.
Cheers,

Julien

Note:
$ dpkg -l |egrep -i '(digikam|kipi)'
ii  digikam
2:1.9.0-1ubuntu1                           digital photo management
application for KDE
ii  digikam-data
2:1.9.0-1ubuntu1                           digikam
architecture-independant data
ii  digikam-dbg
2:1.9.0-1ubuntu1                           debugging symbols for
digikam
ii  digikam-doc
1.2~svn1134171-1                           handbook for digikam and
showfoto in several languages
ii  kipi-plugins
1.9.0-1ubuntu2                             image manipulation/handling
plugins for KIPI aware programs
ii  kipi-plugins-common
1.9.0-1ubuntu2                             kipi-plugins
architecture-independent data
rc  libkipi7
4:4.5.5-0ubuntu2                           library for apps that want
to use kipi-plugins (runtime version)
ii  libkipi8
4:4.6.2-0ubuntu1                           library for apps that want
to use kipi-plugins (runtime version)

For gdb debugging, I'm using the following script
set logging on
set logging file gdb.txt
handle SIG33 pass nostop noprint
set pagination 0
run
backtrace full
info threads
thread apply all backtrace
quit

anything which could help you ?



More information about the Digikam-users mailing list