[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor
https://bugs.kde.org/show_bug.cgi?id=405017 --- Comment #10 from Nate Graham --- *** This bug has been marked as a duplicate of bug 405210 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor
https://bugs.kde.org/show_bug.cgi?id=405017 --- Comment #9 from skierpage --- KDE Frameworks 5.58.0 seems to have fixed the crash \o/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor
https://bugs.kde.org/show_bug.cgi?id=405017 --- Comment #8 from skierpage --- (In reply to Alexander Stippich from comment #7) > This should be fixed by > https://phabricator.kde.org/R286:6e449d44bb5dd7aca58464306d0b7da1312be8ee > which was included in KF 5.56 Sadly I still get a crash with KDE Frameworks 5.57. I left this as a duplicate and added the new stack trace to bug 404565 comment 11. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor
https://bugs.kde.org/show_bug.cgi?id=405017 Nate Graham changed: What|Removed |Added Latest Commit||https://phabricator.kde.org ||/R286:6e449d44bb5dd7aca5846 ||4306d0b7da1312be8ee Version Fixed In||5.56 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor
https://bugs.kde.org/show_bug.cgi?id=405017 Alexander Stippich changed: What|Removed |Added CC||a.stipp...@gmx.net --- Comment #7 from Alexander Stippich --- This should be fixed by https://phabricator.kde.org/R286:6e449d44bb5dd7aca58464306d0b7da1312be8ee which was included in KF 5.56 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor
https://bugs.kde.org/show_bug.cgi?id=405017 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #6 from Nate Graham --- *** This bug has been marked as a duplicate of bug 404565 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor
https://bugs.kde.org/show_bug.cgi?id=405017 --- Comment #5 from skierpage --- Created attachment 118727 --> https://bugs.kde.org/attachment.cgi?id=118727=edit New crash information added by DrKonqi baloo_file_extractor (5.55.0) using Qt 5.11.3 - What I was doing when the application crashed: On restart I guess baloo tried to index a problem file again, and it reported a crash. The backtrace includes Exiv2Extractor:fetchGpsAltitude. `exiv2 print -p a`reports pretty similar GPSAltitude info in the problem file compared to a working panorama, so maybe it isn't the value but the structure or size of the image and its metadata. -- Backtrace (Reduced): #8 0x7f1620856278 in std::__replacement_assert (__file=__file@entry=0x7f162096ff08 "/usr/include/c++/8/bits/stl_vector.h", __line=__line@entry=950, __function=__function@entry=0x7f16209cc740 >::operator[](unsigned long) const::__PRETTY_FUNCTION__> "std::vector<_Tp, _Alloc>::const_reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) const [with _Tp = unsigned char; _Alloc = std::allocator; std::vector"..., __condition=__condition@entry=0x7f162096fed8 "__builtin_expect(__n < this->size(), true)") at /usr/include/c++/8/x86_64-redhat-linux/bits/c++config.h:2389 #9 0x7f162090dc85 in std::vector >::operator[] (__n=, this=) at /usr/src/debug/exiv2-0.26-12.fc29.x86_64/src/value.cpp:229 #10 Exiv2::DataValue::write (os=..., this=) at /usr/src/debug/exiv2-0.26-12.fc29.x86_64/src/value.cpp:233 #11 0x7f162090dcb9 in Exiv2::DataValue::toLong (this=, n=) at /usr/include/c++/8/bits/stl_vector.h:948 #12 0x7f1620fcb56c in KFileMetaData::Exiv2Extractor::fetchGpsAltitude (this=, data=...) at /usr/include/c++/8/ext/aligned_buffer.h:74 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor
https://bugs.kde.org/show_bug.cgi?id=405017 skierpage changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #4 from skierpage --- The Google Pixel 2 panorama JPG file that crashes baloo file indexer is too big to attach at 6,502,554 bytes. It's on https://www.skierpage.com/ in a folder named /bugs, named PANO_20190217_130422.vr.jpg , together with another panorama that's smaller that *doesn't* crash named PANO_20190217_130355.vr.jpg. The crasher is 9112x1670 pixels. The rest of the data reported by ImageMagick's `identify -verbose` seems pretty similar. BTW as comment 3 indicates Fedora upgraded me to a newer version of Plasma/Frameworks than the original comment. Maybe this bug should be refiled against exiv2-libs, perhaps in http://dev.exiv2.org/projects/exiv2/issues ? But I tried all variations of `exiv2 print -p s|a|e|t|v|h|i|x|c|p|C|R|S|X PANO_bad.jpg` and got no crashes. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor
https://bugs.kde.org/show_bug.cgi?id=405017 skierpage changed: What|Removed |Added CC||skierp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor
https://bugs.kde.org/show_bug.cgi?id=405017 --- Comment #2 from skierpage --- (In reply to Nate Graham from comment #1) > You can run `balooctl status` to see which file it crashes on. That didn't help, it just prints the status of the index. Instead I moved all the pictures to (unindexed) /tmp, then `balooctl disable`, `balooctl enable`, and after it had caught up, I moved each file back in a loop. It's crashing on a 6.5 MB Google Panorama photo. I then ran `balooctl index ~/Pictures/2019/PANO_20190217_130422.vr.jpg` and got a third crash: Indexing /home/spage/Pictures/2019/PANO_20190217_130422.vr.jpg /usr/include/c++/8/bits/stl_vector.h:950: std::vector<_Tp, _Alloc>::const_reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) const [with _Tp = unsigned char; _Alloc = std::allocator; std::vector<_Tp, _Alloc>::const_reference = const unsigned char&; std::vector<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__builtin_expect(__n < this->size(), true)' failed. KCrash: Application 'balooctl' crashing... I'll try to link in the Crash Reporting Assistant and attach the big image... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor
https://bugs.kde.org/show_bug.cgi?id=405017 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||n...@kde.org Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- You can run `balooctl status` to see which file it crashes on. -- You are receiving this mail because: You are watching all bug changes.
