[Digikam-devel] [digikam] [Bug 340389] digiKam crashes while editing pictures for color balancing on OSX [patch]

via KDE Bugzilla bugzilla_noreply at kde.org
Sun Jul 3 13:29:28 BST 2016


https://bugs.kde.org/show_bug.cgi?id=340389

--- Comment #34 from caulier.gilles at gmail.com ---
MAik,

The crash do not appear to be in algorithm itself. With my CLI color balance
test tool, it do not crash and color changes are well applied :

bash-3.2$ uname -a
Darwin MacBook-Pro-de-Gilles.local 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr
19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64
bash-3.2$ pwd
/Users/gilles/Devel/GIT/5.x/core/tests/dimg
bash-3.2$ ./testcolorbalancefilter DSC02442.JPG 
digikam.dimg: "DSC02442.JPG"  : JPEG file identified
QCoreApplication::arguments: Please instantiate the QApplication object first
digikam.metaengine: Loading image history  "<?xml version=\"1.0\"?>\n<history
version=\"1\">\n    <filter filterName=\"digikam:LocalContrastFilter\"
filterDisplayName=\"Local Contrast Filter\" filterVersion=\"2\"
filterCategory=\"reproducible\" branch=\"true\">\n        <params>\n           
<param name=\"functionId\" value=\"0\"/>\n            <param
name=\"highSaturation\" value=\"100\"/>\n            <param
name=\"lowSaturation\" value=\"95\"/>\n            <param name=\"randomSeed\"
value=\"1657671516\"/>\n            <param name=\"stage[0]:blur\"
value=\"76\"/>\n            <param name=\"stage[0]:enabled\" value=\"true\"/>\n
           <param name=\"stage[0]:power\" value=\"29.6\"/>\n            <param
name=\"stage[1]:enabled\" value=\"false\"/>\n            <param
name=\"stage[2]:enabled\" value=\"false\"/>\n            <param
name=\"stage[3]:enabled\" value=\"false\"/>\n            <param
name=\"stretchContrast\" value=\"true\"/>\n        </params>\n    </filter>\n  
 <file
uuid=\"7174ee148022418aa609b3eee909b8497ee276a2418bb8df86bffe28714adbbc\">\n   
    <fileParams fileHash=\"8323daada84da3cebe83fcc08230e5db\"
fileSize=\"3734050\"/>\n    </file>\n    <filter
filterName=\"digikam:RatioCrop\" filterDisplayName=\"Aspect Ratio Crop\"
filterVersion=\"1\" filterCategory=\"reproducible\">\n        <params>\n       
    <param name=\"height\" value=\"3867\"/>\n            <param name=\"width\"
value=\"5800\"/>\n            <param name=\"x\" value=\"199\"/>\n           
<param name=\"y\" value=\"133\"/>\n        </params>\n   
</filter>\n</history>\n"
digikam.metaengine: DateTime => Exif.Photo.DateTimeOriginal => 
QDateTime(2014-05-01 16:49:11.000 CEST Qt::TimeSpec(LocalTime))
digikam.dimg: Saving to  "DSC02442.out.png"  with format:  "PNG"
digikam.metaengine: MetaEngine::metadataWritingMode 0
digikam.metaengine: Will write Metadata to file
"/Users/gilles/Devel/GIT/5.x/build/core/tests/dimg/DSC02442.out.png"
digikam.metaengine: wroteComment:  true
digikam.metaengine: wroteEXIF:  true
digikam.metaengine: wroteIPTC:  true
digikam.metaengine: wroteXMP:  true
digikam.metaengine: Metadata for file "DSC02442.out.png" written to file.

The only difference is that filter is forked in a dedicated thread. Perhaps
it's the problem.

Gilles

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Digikam-devel mailing list