| Summary: | crash when reading nef data: Warning: Exif tag Exif.NikonPreview.JPEGInterchangeFormatLength not encoded | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | jdanne <jdanne> |
| Component: | Metadata-Raw | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | ahuggel, caulier.gilles, marcel.wiesweg |
| Priority: | NOR | ||
| Version: | 0.10.0 | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.0.0 | |
| Sentry Crash Report: | |||
| Attachments: | Obviously this file did crash digikam. | ||
|
Description
jdanne
2009-12-27 22:52:01 UTC
Exiv2 library relevant. 1/ Use last digiKam 1.0.0 2/ use last Exiv2 0.18.2 3/ update libkexiv2 and kipi-plugins. 4/ Look in Help/Comopnents Info if all is fine with versions. 5/ try again. 6/ If it crash again, try to find the image relevant and give us a link to download and test. Gilles Caulier Hello Caulier,
obviously the attached file caused digkam to crash.
Best regards
Joerg
Am Sonntag, 27. Dezember 2009 22:56:43 schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=220322
>
>
> Gilles Caulier <caulier.gilles@gmail.com> changed:
>
> What |Removed |Added
> ---------------------------------------------------------------------------
> - CC| |ahuggel@gmx.net
> Component|general |Metadata
> Version|unspecified |0.10.0
>
>
>
>
> --- Comment #1 from Gilles Caulier <caulier gilles gmail com> 2009-12-27
> 22:56:42 --- Exiv2 library relevant.
>
> 1/ Use last digiKam 1.0.0
> 2/ use last Exiv2 0.18.2
> 3/ update libkexiv2 and kipi-plugins.
> 4/ Look in Help/Comopnents Info if all is fine with versions.
> 5/ try again.
> 6/ If it crash again, try to find the image relevant and give us a link to
> download and test.
>
> Gilles Caulier
>
Joerg, Could you please attach the file. It hasn't come through on the bug tracking system. Thanks, Mark Created attachment 39398 [details]
Obviously this file did crash digikam.
Crash is clearly reproducable with exiv2 command line utility and current trunk. It's a PNG file btw. Filed report at http://dev.exiv2.org/issues/show/664 please watch progress there. On Monday 28 December 2009 23:13:30 Marcel Wiesweg wrote: > Crash is clearly reproducable with exiv2 command line utility and current > trunk. It's a PNG file btw. > Filed report at > http://dev.exiv2.org/issues/show/664 > please watch progress there. This is terrible! Whilst I understand the core issue with exiv2, the inability to handle this error condition in multiple KDE applications is very severe. This runs contrary to the Robustness Principle.[1] Imagine if this image was placed on a prominent web site, such as google, or even a series of anti FOSS sites. Mark [1] http://en.wikipedia.org/wiki/Robustness_principle Yes it's true crashes should never occur. The only workaround would be to move actual file access into a separate process and watch for crashes. Amarok does or did that for it's scanning process. It's a huge work and overhead. In our experience it's only the odd photo here and there leading to exiv2 crashes. Exiv2's development pace is fast. That means occasionally a crash will slip in. It's the same in every project. But it's very well maintained and communication is excellent, see that the issue is fixed after a day. Not reproducible with digiKam 7.0.0-beta1. |