Bug 366034 - Crash at edit metadata for jpgs made by a Casio EX-Z500
Summary: Crash at edit metadata for jpgs made by a Casio EX-Z500
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Engine (show other bugs)
Version: 5.0.0
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-24 12:54 UTC by Wolfram Kroiss
Modified: 2021-05-04 04:09 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.3.0


Attachments
Image that leads to the crash (2.57 MB, image/jpeg)
2016-07-24 12:54 UTC, Wolfram Kroiss
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfram Kroiss 2016-07-24 12:54:26 UTC
Created attachment 100266 [details]
Image that leads to the crash

Select a jpg made by a Casio Exilim Z500 camera (see the attached image as an example) and try to edit metadata (Menu Item->Edit Metadata...). digikam shows a runtime error popup and exits.

Similar behavior in version 4.12.0. Reason for the crash is an memory access violation according to v4.12.0 error popup.

One example is attached but the crash happens with all images that were made with this camera.
Comment 1 caulier.gilles 2016-07-24 13:24:18 UTC
It's probably due to  crash inside Exiv2 shared library. Metadata Editor read information in image trough this shared library. 

Please report this problem to Exiv2 team with your suspected image for investigations.

http://dev.exiv2.org/projects/exiv2/issues

Gilles Caulier
Comment 2 Wolfram Kroiss 2016-07-24 13:26:40 UTC
No problems with manipulating these files using exiv2.exe (v0.25) though.
Comment 3 Wolfram Kroiss 2016-07-24 13:41:28 UTC
(In reply to caulier.gilles from comment #1)
> It's probably due to  crash inside Exiv2 shared library. Metadata Editor
> read information in image trough this shared library. 
> 
> Please report this problem to Exiv2 team with your suspected image for
> investigations.
> 
> http://dev.exiv2.org/projects/exiv2/issues
> 
> Gilles Caulier

Thanks for the hint. This problem seems to be known at exiv2 and a fix is going to be released with version 0.26 which is due end of July 2016 (in a week from now).
Comment 4 caulier.gilles 2021-05-04 04:09:44 UTC
Not reproducible with digiKam 7.3.0 and Exiv2 0.27.4