https://bugs.kde.org/show_bug.cgi?id=399923
--- Comment #91 from caulier.gil...@gmail.com --- Maik, Perhaps the best way to try to catch exactly the problem is to isolate the threadimageio code used by Face management in an unit test, and to run this code around a large set of images to parse. This can reveal (or not) some problems. If you can reproduce the problem with an unit test, this want mean certainly that problem is more in-deep in face management level, as i suspect. The crash in preview code is just a side effect due to memory corruption. After an analyze of current code, i don't understand why the wrong virtual method is called in place. The advantage to use QTest API is that lots of tools available from CLI to proof, benchmark, and hack the code while running. The integration with KDE CI following all commit permit to check is somebody has broken something in core API. Look my recent work with meta-engine unit tests, used to consolidate the Exiv2 interface. Gilles -- You are receiving this mail because: You are watching all bug changes.
