| Summary: | baloo_file_extractor crashes in Exiv2::Internal::TiffReader::readTiffEntry() on a specific TIFF file | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kfilemetadata | Reporter: | Nicolas Fella <nicolas.fella> |
| Component: | general | Assignee: | Pinak Ahuja <pinak.ahuja> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | nate, tu4manjohn |
| Priority: | NOR | ||
| Version First Reported In: | 5.56.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Backtrace
Backtrace with debug symbols |
||
I was able to pinpoint the crash to a file: https://cgit.kde.org/digikam.git/tree/core/tests/metadataengine/data/20160821035715.jpg Crashing in Exiv2::Internal::TiffReader::readTiffEntry. It's interesting that you say it crashes on a JPEG file, because KFileMetadata was trying to open it as a TIFF. It's possible this is fixed in git master/5.57 due to improvements in file type detection; can you test? Created attachment 119273 [details]
Backtrace with debug symbols
Still happens with Neon unstable Relevant part of the backtrace: #17 0x00007fd23bcada06 in Exiv2::TiffParser::decode(Exiv2::ExifData&, Exiv2::IptcData&, Exiv2::XmpData&, unsigned char const*, unsigned int) () from /usr/lib/x86_64-linux-gnu/libexiv2.so.26 #18 0x00007fd23bc29330 in Exiv2::ExifParser::decode(Exiv2::ExifData&, unsigned char const*, unsigned int) () from /usr/lib/x86_64-linux-gnu/libexiv2.so.26 #19 0x00007fd23bc43170 in Exiv2::JpegBase::readMetadata() () from /usr/lib/x86_64-linux-gnu/libexiv2.so.26 #20 0x00007fd24004d208 in KFileMetaData::Exiv2Extractor::extract (this=0x5639d84966f0, result=0x7ffece28b320) at ./src/extractors/exiv2extractor.cpp:163 #21 0x00005639d6eb022f in Baloo::App::index (this=this@entry=0x7ffece28bac0, tr=0x5639d8abbc80, url=..., id=id@entry=5642697968715777) at ./src/file/extractor/app.cpp:192 #22 0x00005639d6eb0b8e in Baloo::App::processNextFile (this=0x7ffece28bac0) at ./src/file/extractor/app.cpp:112 So Exiv2 first (correctly) tries the JPEG extractor, then switches to the TIFF extractor for some reason, then crashes. At this point it feels like the issue is in Exiv2 itself, not Baloo or KFileMetadata, both of which have done their part as much as they're able. Can you file a bug with the Exiv2 folks? The fully symbolicated backtrace you attached will probably be very useful for them. Thanks! Looks like the issue is resolved in exiv master Do you have a link to the commit handy? Then I can see about prodding the discrete release distros to patch their Exiv packages. Sorry, I don't |
Created attachment 119243 [details] Backtrace SOFTWARE/OS VERSIONS KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56 Qt Version: 5.12.2 ADDITIONAL INFORMATION