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

            Bug ID: 490730
           Summary: Crash in image editor.
    Classification: Applications
           Product: digikam
           Version: 8.5.0
          Platform: Microsoft Windows
                OS: Microsoft Windows
            Status: REPORTED
          Severity: crash
          Priority: NOR
         Component: ImageEditor-Core
          Assignee: digikam-bugs-n...@kde.org
          Reporter: j...@acm.org
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
Pull up the image editor and maybe do a little work and it crashes.
this only happens sometimes.  

STEPS TO REPRODUCE
I have been in a cycle of:

1:  Select an image in tile mode (happens with preview as well).
2:  Open the editor for this image (will be either tiff or jpg).
3:  (only for some images) free rotate using the set points.
4:  crop the overscanned edges.
5:  (for some images, one or more of):  auto colors, curve colors, or
brightness, contrast, gamma.
6:  Save the image as TIFF.
7:   Close the editor
8:  Repeat from 1:
9:  Occasionally select all of the files done and turn off a tag reminding me
which images have not gone through this step.

OBSERVED RESULT
Crash in the editor.  Debug with no symbols for this dll.  

Unhandled exception at 0x00007FFA533246A0 (Qt6Widgets.dll) in digikam.exe:
0xC0000005: Access violation reading location 0x0000000000000020.

EXPECTED RESULT
No crash.

SOFTWARE/OS VERSIONS
Windows: 11
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Build date: 7/22/2024 8:05 PM (target: RelWithDebInfo)
Revision: 3e387a3d137e97d730422b30ca398e69829382ec
Branch: master

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to