https://bugs.kde.org/show_bug.cgi?id=405017
--- Comment #2 from skierpage <skierp...@gmail.com> --- (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<unsigned char>; 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.
