Bug 262000 - Kioslave crashes during batch rename
Summary: Kioslave crashes during batch rename
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: AdvancedRename-engine (show other bugs)
Version: 1.7.0
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-03 21:16 UTC by Martin Foster
Modified: 2020-08-12 08:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Foster 2011-01-03 21:16:51 UTC
Version:           1.7.0 (using KDE 4.4.4) 
OS:                MS Windows

During a batch rename of 39 images, kioslave crashed on two seperate occasions with the following error message: "Kioslave.exe has stopped working" ... blah ... blah ... blah. 

Here's the debug output:
---------- 8< ----------
Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	kioslave.exe
  Application Version:	0.0.0.0
  Application Timestamp:	4c0edde2
  Fault Module Name:	QtDBus4.dll
  Fault Module Version:	4.6.2.0
  Fault Module Timestamp:	4b92e14c
  Exception Code:	c0000005
  Exception Offset:	0002ae3e
  OS Version:	6.1.7600.2.0.0.768.3
  Locale ID:	2057
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789
---------- 8< ----------

However, regardless of the fact that Kioslave crashed twice, the batch rename process continued and completed successfully. 

This is the template I was using for the batch rename: "LS-#####[1536]_[file]", incrementing each file number by one.

Reproducible: Always
Comment 1 caulier.gilles 2011-01-04 08:35:42 UTC
We need more information about. Into KDE bin dir, there are some programs to use :

1/ Run kdebugdialog and turn on right digiKam/kipi debug spaces.

2/ Before to run digiKam, run debugview program to see all debug messages printed by KDE and digiKam . This is similar of console trace.

3/ Reproduce the trace and post here all debug trace for investiguation.

Gilles Caulier
Comment 2 Martin Foster 2011-01-04 15:00:07 UTC
OK, I've done that and I have numerous traces here because I'm having LOTS of trouble:

[1] The batch rename job completes without any problems whatsoever.
[2] The batch rename job completes but Kioslave crashes during the job.
[3] The batch rename job does NOT complete because digiKam crashes!

Which trace(s) do you want?
Comment 3 Martin Foster 2011-01-04 15:25:35 UTC
I've just noticed something:

Currently, I don't have digiKam running but I have 12 instances of kioslave.exe running - eh??!!
Comment 4 Martin Foster 2011-01-05 12:25:48 UTC
(In reply to comment #1)
> We need more information about. Into KDE bin dir, there are some programs to
> use :
> 
> 1/ Run kdebugdialog and turn on right digiKam/kipi debug spaces.
> 
> 2/ Before to run digiKam, run debugview program to see all debug messages
> printed by KDE and digiKam . This is similar of console trace.
> 
> 3/ Reproduce the trace and post here all debug trace for investiguation.
> 
> Gilles Caulier

I've selected 3 traces for you to have a look at but they're far too big to post here, so I've zip'd them up and put the zip archive in my dropbox for you (or anybody else) to download. 

Here's the link: http://dl.dropbox.com/u/9712127/windows/Projects/digiKam-Windows/digikam_traces_01.zip
Comment 5 Andi Clemens 2011-03-06 11:43:16 UTC
The best thing would be to ignore media types that are not images in the progress bar dialog. The problem with crashing could arise in other places, too.

Gilles,

what do you think? Should we just skip displaying a thumbnail for video, audio and other types when showing the graphical progress bar dialog?

Andi
Comment 6 caulier.gilles 2011-12-15 08:09:16 UTC
This file still valid using digiKam 2.3.0 for windows ?

Gilles Caulier
Comment 7 Ananta Palani 2013-06-10 13:02:18 UTC
(In reply to comment #4)
> (In reply to comment #1)
> > We need more information about. Into KDE bin dir, there are some programs to
> > use :
> > 
> > 1/ Run kdebugdialog and turn on right digiKam/kipi debug spaces.
> > 
> > 2/ Before to run digiKam, run debugview program to see all debug messages
> > printed by KDE and digiKam . This is similar of console trace.
> > 
> > 3/ Reproduce the trace and post here all debug trace for investiguation.
> > 
> > Gilles Caulier
> 
> I've selected 3 traces for you to have a look at but they're far too big to
> post here, so I've zip'd them up and put the zip archive in my dropbox for
> you (or anybody else) to download. 
> 
> Here's the link:
> http://dl.dropbox.com/u/9712127/windows/Projects/digiKam-Windows/
> digikam_traces_01.zip

Hi Martin,

Could you try this out with digiKam 3.1.0? A lot of changes were made in regard to renaming files and temporary file names:
   http://download.kde.org/stable/digikam/digiKam-installer-3.1.0-win32.exe
Comment 8 caulier.gilles 2015-06-30 08:07:51 UTC
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?
Comment 9 caulier.gilles 2015-07-06 07:39:52 UTC
digiKam 4.11.0 Windows installer is available for download :

http://download.kde.org/stable/digikam/digiKam-installer-4.11.0-win32.exe.mirrorlist
Comment 10 caulier.gilles 2015-08-24 05:13:32 UTC
digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.
Comment 11 caulier.gilles 2016-05-28 18:24:30 UTC
With next digiKam 5.0.0, we will provide a fully cross-compiled version Windows under Linux where a lots of problems have been fixed.

https://www.flickr.com/photos/digikam/27033685570/in/dateposted-public/

The Windows installer is available here to test :

https://drive.google.com/open?id=0B7yq-xFihT0_SzhxVzF1RDhPbFE

Gilles Caulier