https://bugs.kde.org/show_bug.cgi?id=425096
--- Comment #8 from Proffecanded ---
Yes I did. I compiled it with mxe.
Could it be related to a memory leak or the bug was fixed in version 7.1.0.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=425096
--- Comment #6 from Proffecanded ---
I can't reproduce bug with commit 536c505d96df7434c30a2a94e03e57759f686186.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=425096
--- Comment #5 from Proffecanded ---
I set the environment variable and found the image causing crash. It's a 70MB
panoramic photo. I tried to scan again the whole folder but digikam doesn't
crash anymore.
I've compiled latest version
https://bugs.kde.org/show_bug.cgi?id=425096
--- Comment #2 from Proffecanded ---
How I can find the image causing the crash?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=425096
Bug ID: 425096
Summary: Crash Unsupported JPEG process: SOF type 0xc8
Product: digikam
Version: 7.0.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
