Bug 417896 - Crash while converting RAW (Canon cr2) files (V 7 Beta 2)
Summary: Crash while converting RAW (Canon cr2) files (V 7 Beta 2)
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: BatchQueueManager-RAWProcessing (other bugs)
Version First Reported In: 7.0.0
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-19 21:45 UTC by Nigel Aves
Modified: 2022-01-13 11:19 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nigel Aves 2020-02-19 21:45:16 UTC
SUMMARY

digiKam version 7 Beta 2

If I select one or two RAW images for processing all works OK.

But after getting the "queue" setup, I selected approx 100 RAW images for processing. These were created on a Canon 5Ds (8688x5792 pixels - 58 Meg file size)

Sometimes it has processed approx 50 photographs before crashing, last run only 8 or 9.

Here is the output from the terminal. I don't know where there is a core dump to send you (sorry, I'm very new to Linux on a desktop.)

Digikam::WBFilter::autoExposureAdjustement: Black: 0.0722656   Exposition: 0.00564656
Digikam::WBFilter::filterImage: T(K): 6500 => R: 1.00223    G: 1.00574    B: 1.0221   BP: 18   WP: 255
Digikam::Task::run: Tool : index=  2  :: name=  "WhiteBalance"  :: group=  2  :: wurl=  QUrl("file:///home/nigel/Pictures/processed/")
Digikam::BatchTool::setOutputUrlFromInputUrl: path:  "/home/nigel/Pictures/processed/BatchTool-rwYChM-7f1526b7.digikamtempfile.CR2"
Digikam::BatchTool::apply: Tool:        ""
Digikam::BatchTool::apply: Input url:   QUrl("file:///home/nigel/Pictures/processed/BatchTool-fGSEWK-f099884a.digikamtempfile.CR2")
Digikam::BatchTool::apply: Output url:  QUrl("file:///home/nigel/Pictures/processed/BatchTool-rwYChM-7f1526b7.digikamtempfile.CR2")
Digikam::WBFilter::autoExposureAdjustement: White level at: 229
Digikam::WBFilter::autoExposureAdjustement: Black: 0.0136719   Exposition: 0.15451
Digikam::WBFilter::filterImage: T(K): 6500 => R: 1.00223    G: 1.00574    B: 1.0221   BP: 3   WP: 230
/tmp/.mount_digikaY7c989/AppRun: line 155: 22479 Segmentation fault      (core dumped) digikam $@


STEPS TO REPRODUCE
Assigned tools

Color Auto-correction
White Balance
Anti-Vignetting
Sharpen Image
Film Grain
Add Watermark (using text)
Resize
Convert to JPEG

OBSERVED RESULT

Must have a moth shorting out my back-plane!

EXPECTED RESULT


SOFTWARE/OS VERSIONS

Linux version 5.3.0-40-generic (buildd@lcy01-amd64-026) (gcc version 9.2.1 20191008) 

#32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 (Ubuntu 5.3.0-40.32-generic 5.3.18)

KDE Frameworks 5.65.0
Qt 5.14.0 (built against 5.14.0)
The xcb windowing system

ADDITIONAL INFORMATION

If there is anything I can do my end to help, please let me know. More than happy to help.
Comment 1 caulier.gilles 2020-02-19 21:57:05 UTC
You run the AppImage. From the console, pass "debug" as argument. This will start digiKam in debugger. When it crash you will get a prompt, where just entry "bt" for backtrace.

For info is given here :

https://www.digikam.org/contribute/

Gilles Caulier
Comment 2 Maik Qualmann 2020-02-19 21:59:40 UTC
Do you use all processor cores in BQM? It is possible that you are running out of memory.

Maik
Comment 3 Nigel Aves 2020-02-19 23:05:31 UTC
Here is the trace-back.  I will now run it with "multi-core" turned off, so Yes, I was using it. Interesting though. The first time I ran this with "debug" it worked all the way through 193 photographs. The 2nd time it crashed before processing a single photograph. I have 32 GB of memory / AMD Ryzen 7.

Trace back ....


Thread 1209 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff627fc700 (LWP 30627)]
0x00007ffff779313d in Digikam::WBFilter::adjustWhiteBalance(unsigned char*, int, int, bool) () from /tmp/.mount_digikaMSxxwt/usr/lib/libdigikamcore.so.7.0.0


(gdb) bt
#0  0x00007ffff779313d in Digikam::WBFilter::adjustWhiteBalance(unsigned char*, int, int, bool) () from /tmp/.mount_digikaMSxxwt/usr/lib/libdigikamcore.so.7.0.0
#1  0x00007ffff7793878 in Digikam::WBFilter::filterImage() () from /tmp/.mount_digikaMSxxwt/usr/lib/libdigikamcore.so.7.0.0
#2  0x00007ffff772a858 in Digikam::AutoExpoFilter::filterImage() () from /tmp/.mount_digikaMSxxwt/usr/lib/libdigikamcore.so.7.0.0
#3  0x00007ffff76d9968 in Digikam::DImgThreadedFilter::startFilterDirectly() () from /tmp/.mount_digikaMSxxwt/usr/lib/libdigikamcore.so.7.0.0
#4  0x00007ffff6e7c767 in Digikam::BatchTool::applyFilter(Digikam::DImgThreadedFilter*) () from /tmp/.mount_digikaMSxxwt/usr/lib/libdigikamgui.so.7.0.0
#5  0x00007fffc8451038 in ?? () from /tmp/.mount_digikaMSxxwt/usr/plugins/digikam/bqm/Bqm_AutoCorrection_Plugin.so
#6  0x00007ffff6e7d8b4 in Digikam::BatchTool::apply() () from /tmp/.mount_digikaMSxxwt/usr/lib/libdigikamgui.so.7.0.0
#7  0x00007ffff6e7a27d in Digikam::Task::run() () from /tmp/.mount_digikaMSxxwt/usr/lib/libdigikamgui.so.7.0.0
#8  0x00007ffff42f2f47 in ?? () from /tmp/.mount_digikaMSxxwt/usr/lib/libQt5Core.so.5
#9  0x00007ffff42ef4f5 in ?? () from /tmp/.mount_digikaMSxxwt/usr/lib/libQt5Core.so.5
#10 0x00007ffff3c8b669 in start_thread (arg=<optimized out>) at pthread_create.c:479
#11 0x00007ffff3bb3323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Comment 4 Maik Qualmann 2020-02-20 19:27:38 UTC
Git commit 57fb0c388c1fc185f77685a7fb4634e59d6b0692 by Maik Qualmann.
Committed on 20/02/2020 at 19:26.
Pushed by mqualmann into branch 'master'.

add test debug output

M  +2    -0    core/libs/dimg/filters/wb/wbfilter.cpp

https://invent.kde.org/kde/digikam/commit/57fb0c388c1fc185f77685a7fb4634e59d6b0692
Comment 5 caulier.gilles 2020-07-14 09:41:23 UTC
Hi,

Can you check if this problem still exist with last weekly bundle build of digiKam 7.0.0 available here:

https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier
Comment 6 caulier.gilles 2020-07-30 09:45:06 UTC
digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Thanks in advance

Gilles Caulier
Comment 7 caulier.gilles 2021-03-30 06:53:42 UTC
digiKam 7.2.0 official release is published with more than 360 files closed from bugzilla:

https://www.digikam.org/news/2021-03-22-7.2.0_release_announcement/

Can you reproduce the dysfunction with this version ?

Thanks in advance for your feedback

Gilles Caulier
Comment 8 caulier.gilles 2021-12-15 09:26:33 UTC
Nigel,

Stable digiKam 7.4.0 is published. Please check if problem is reproducible.

https://www.digikam.org/download/

Thanks in advance
Comment 9 caulier.gilles 2022-01-13 11:19:23 UTC
No feedback. not reproducible with 7.5.0. Closed