Bug 382818 - Rotating a picture ends in crash
Summary: Rotating a picture ends in crash
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-DImg-JPEG (show other bugs)
Version: 5.6.0
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-27 19:05 UTC by Markus Kempf
Modified: 2017-11-01 04:41 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.8.0
Sentry Crash Report:


Attachments
gdb export after crash (25.05 KB, text/csv)
2017-07-28 10:19 UTC, Markus Kempf
Details
gdb export after crash and bt (33.06 KB, text/csv)
2017-07-28 11:14 UTC, Markus Kempf
Details
rotating this picture results in a crash (2.08 MB, image/jpeg)
2017-08-01 19:23 UTC, Markus Kempf
Details
created jpg during the crash (28.00 KB, image/jpeg)
2017-08-01 19:25 UTC, Markus Kempf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Kempf 2017-07-27 19:05:10 UTC
If I rotate an image (clicking the button) it works one, two times. The next rotation of an image ends in a sudden crash, digikam closes without any bug description or hint. 

It is possible to rotate pictures in the ImageEditor-Tool.

I am using ubuntu 17.04 and unity and with the package source of http://ppa.launchpad.net/philip5/extra/ubuntu
Comment 1 Simon 2017-07-27 20:17:03 UTC
Can you please run digikam in gdb and post the backtrace after the crash as describe here:
https://www.digikam.org/contribute/
Comment 2 Markus Kempf 2017-07-28 10:19:27 UTC
Created attachment 106913 [details]
gdb export after crash
Comment 3 Simon 2017-07-28 11:06:57 UTC
After the segfault instead of quitting directly, you need to first run "bt" to get the backtrace - which is the most essential part of the entire report.
Comment 4 Markus Kempf 2017-07-28 11:14:37 UTC
Created attachment 106914 [details]
gdb export after crash and bt

This time after bt in gdb
Comment 5 Simon 2017-07-28 13:10:14 UTC
I don't see anything obviously problematic in the function the backtrace points to and I can't reproduce the crash here. I am out of my depth here.
Comment 6 Christoph Feck 2017-07-30 13:54:44 UTC
Pasting relevant part from comment #4 for duplicate searches.

(gdb) bt
#0  0x00007ffff677b5c3 in ?? () from /usr/lib/digikam/libdigikamcore.so.5.6.0
#1  0x00007ffff6774458 in Digikam::JPEGUtils::JpegRotator::performJpegTransform(Digikam::MetaEngineRotation::TransformationAction, QString const&, QString const&) () from /usr/lib/digikam/libdigikamcore.so.5.6.0
#2  0x00007ffff67779d7 in Digikam::JPEGUtils::JpegRotator::exifTransform(Digikam::MetaEngineRotation const&) () from /usr/lib/digikam/libdigikamcore.so.5.6.0
#3  0x00007ffff67793f7 in Digikam::JPEGUtils::JpegRotator::exifTransform(Digikam::MetaEngineRotation::TransformationAction) ()
   from /usr/lib/digikam/libdigikamcore.so.5.6.0
Comment 7 Markus Kempf 2017-07-31 21:49:37 UTC
I don't understand the last comment "relevant part for duplicate searches".

I tried to rotate pictures coming from different sources. It seems that jpg-pictures from the camera don't crash during the roting (imported via the import tool), but pictures exported by rawtherapee or cropped by imagemagick show the crashes (created in the folder structure of the digikam).
Comment 8 Maik Qualmann 2017-08-01 06:07:39 UTC
The comment #6 is only for finding similar crashes within the bug tracker. Can you provide an image that triggers a crash?

Maik
Comment 9 Markus Kempf 2017-08-01 19:23:49 UTC
Created attachment 107016 [details]
rotating this picture results in a crash

Rotating this picture ends in a crash of digikam. The picture comes from rawtherapee, is cropped by imagemagick and stored as 85% jpg via gimp. Normally I use 100% jpg but I have to reduce the image size.
Interesting point - after the crash there is a new jpg created in the folder. I will attach it, too.
Comment 10 Markus Kempf 2017-08-01 19:25:01 UTC
Created attachment 107018 [details]
created jpg during the crash

During rotating and crashing of pic 107016 the attached digikamtempfile is created...
Comment 11 Maik Qualmann 2017-08-01 19:45:02 UTC
Which libJPEG version you use, see digiKam component info? Which of the messages below do you see in the console? The LibJPEG error with the "Maximum supported image dimension is 65500 pixels" is strange. But there is no crash here.

digikam.general: Jpegutils error, aborting operation: Maximum supported image dimension is 65500 pixels
digikam.general: JPEG lossless transform failed for "/daten/Bilder/Zugang/bretagne95_m6_P6040736_crop.jpg"
digikam.general: Trying lossy transform for  "/daten/Bilder/Zugang/bretagne95_m6_P6040736_crop.jpg"
digikam.dimg: "/daten/Bilder/Zugang/bretagne95_m6_P6040736_crop.jpg"  : JPEG file identified
digikam.general: JPEG Quality:  85  File:  "/daten/Bilder/Zugang/bretagne95_m6_P6040736_crop.jpg"

Maik
Comment 12 Markus Kempf 2017-08-01 20:08:37 UTC
The digikam component info shows

LibJPEG: 80

ubuntu 17.04 installs 
libjpeg8
JPEG-Laufzeitbibliothek der »Independent JPEG Group« (Abhängigkeitspaket)
Comment 13 Markus Kempf 2017-08-09 20:43:52 UTC
Today I installed digikam 5.4 from the ubuntu package - and this version works! Rotating withoud crash is possible. Reinstalling digikam 5.6 - the problem is back: rotating creates a crash
Comment 14 Markus Kempf 2017-11-01 00:05:12 UTC
I updated to ubuntu 17.10 and installed digikam 5.6.0 - and it works.
So the problem seems solved.