https://bugs.kde.org/show_bug.cgi?id=427760
Johannes Zarl-Zierl <johan...@zarl-zierl.at> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
CC| |johan...@zarl-zierl.at
--- Comment #1 from Johannes Zarl-Zierl <johan...@zarl-zierl.at> ---
Thanks for the bug report, and special thanks for running kphotoalbum with
assertions enabled!
I could reproduce this by copying additional video files to the demo database.
The stack trace shows the following function as the culprit:
DB::FileName nextExistingImage(const DB::FileName &fileName, int frame, int
direction)
{
for (int i = 1; i < 10; ++i) {
const int nextIndex = (frame + 10 + direction * i) % 10;
const DB::FileName file =
BackgroundJobs::HandleVideoThumbnailRequestJob::frameName(fileName, nextIndex);
if (file.exists())
return file;
}
Q_ASSERT(false && "We should always find at least the current frame");
return DB::FileName();
}
I'll have to evaluate the conditions that can lead to this code path in
detail...
--
You are receiving this mail because:
You are watching all bug changes.
