[Digikam-devel] [Bug 241536] reproducible crash when bilding fingerprint

[Axel Krebs]

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





--- Comment #6 from Axel Krebs <axel krebs t-online de>  2010-06-13 17:14:55 ---
Am 13.06.2010 15:22, schrieb Marcel Wiesweg:
> https://bugs.kde.org/show_bug.cgi?id=241536
>
>
> --- Comment #5 from Marcel Wiesweg<marcel wiesweg gmx de>   2010-06-13 15:22:26 ---
> I can fully reproduce the crash on my computer, in 100% of cases with certain
> panorama images.
> dimgscale.cpp is 2000 lines of manually optimized scaling code, without
> comments of meaningful variable names, not written or completely understood by
> anyone of us in the team.
> Probably, a few hours of careful study would be needed to understand and fix
> what's wrong here.
>

If "only" a few hours where needed to find the failure cause, wouldn't 
this be worth? It looks to me, dimgscale.cpp might be quite a bottleneck 
for DigiKam 
<http://digikam.sourcearchive.com/documentation/2:0.9.2-2ubuntu2/files.html>. 

---

Question: if hardware is _not_ the reason, makes it sense to narrow the 
very files: type, versions, sizes e.g.?
---

I published my database statistics from DigiKam; the statistic seems 
complete, but does _not_ distinguish several fine variations: is there a 
better detailed statistic available?
---

I know there are many "dialects" for gif, tif(f), raw (nef, cr2, crw,..) 
and so on.

And I know from an older (cheap) Canon Powershot A710 IS, and, less, 
from Canon Powershot A720 IS, that these models mistake exif-data (wrong 
date and time in raw, correct date and time in jpg, e.g.)

Besides, exif standard changed themselfes within the last couple of years:
<http://de.wikipedia.org/wiki/Exchangeable_Image_File_Format>
<http://www.exif.org/specifications.html>

So I ask myself, how should DigiKam handle "old" exif-data right?
---

I am afraid, I (would like but) cannot helf do programming work.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.