https://bugs.kde.org/show_bug.cgi?id=386098
--- Comment #6 from Johannes Hirte <johannes.hi...@datenkhaos.de> --- Yes, it's a very nasty bug, and I'm still not sure if this may be a bug in Qt or some other component. But I've seen this only with digikam. And it smells like some race condition to me. In the past, I've seen this once a day or more. With current digikam, I get this once a month. I have some more backtraces, always ending in: QHashData::nextNode As digikam is highly multithreaded, mabye the thread-sanitizer can light this up. -- You are receiving this mail because: You are watching all bug changes.
