Summary: | Digikam "spontaneous" crash | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Heikki Välisuo <heikki.valisuo> |
Component: | Thumbs-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 1.3.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.6.0 | |
Sentry Crash Report: |
Description
Heikki Välisuo
2010-08-15 11:41:34 UTC
This looks like a issue deep inside libjpeg which is used by digikam. Please report the problem to the libjpeg developers. Thinking about this once again it may also have been cause by a memory leak that existed in 1.3. Marcel, what do you think? Happens in libjpeg when loading a file for thumbnailing. For a memory leak, out of memory, I would expect a failed new or malloc() call, this really looks like a plain invalid memory access. Heikki, can you reproduce? Do you know which file was causing this? It is probably a JPEG file, and the filename was probably printed on the console before the crash occurred. Hi Marcel, Sorry, I am afraid I cannot give any useful details. Some backgroud: I had copied nearly 30000 photos in my new computer. I asked digikam show me the main album with all its subalbums in the thumbnail view. Because I did not copy the old thumbnails database, digikam was creating new thumbnails to all the photos. Quite a long time before the crash I noticed that at least one of the thumbnails was incorrect. I could not recognise the thumbnail. Maybe it was a small part of the photo or something else. Because the photo was not too interesting, I deleted the photo. What I want to tell is that I had been all kind of things with a large collection of photos and may have corrupted some of them. In the evening I can delete the thumbnails database and make digikam recreate it. If it crashes again, then we have something. |