https://bugs.kde.org/show_bug.cgi?id=393635
caulier.gil...@gmail.com changed:
What|Removed |Added
Severity|normal |crash
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=393635
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In||6.3.0
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=393635
Victor Engmark changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #27 from caulier.gil...@gmail.com ---
why do you want to use an instable version (beta3).
6.2.0 official release is published :
https://download.kde.org/stable/digikam/6.2.0/
Gilles Caulier
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #26 from Victor Engmark ---
I downloaded and verified the image:
$ wget --continue
https://download.kde.org/unstable/digikam/digikam-6.0.0-beta3-20181228T114626-x86-64.appimage
https://bugs.kde.org/show_bug.cgi?id=393635
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In|6.2.0 |
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=393635
caulier.gil...@gmail.com changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=393635
Victor Engmark changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #23 from caulier.gil...@gmail.com ---
Victor,
This crash still reproducible using last Linux AppImage bundle 6.2.0 pre
release available here : https://files.kde.org/digikam/
Thanks in advance
Gilles Caulier
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #22 from Maik Qualmann ---
I have let the address of all DMetadata objects debugged and even if they are
destroyed. In principle, when the crash occurs, there is current no more
DMetadata object in memory.
Maik
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #21 from Maik Qualmann ---
I think that QMutex will not help us here. It crashes in
PreviewLoadingTask::loadImagePreview(), which I can reproduce well if I click
on the image right after the start. But moving the function into the
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #20 from caulier.gil...@gmail.com ---
Maik,
Forget to said that we will need to lock all calls to DK Metadata Engine with
Mutex, as the next 0.27 will take few months to be released and we will need to
support Exiv2 0.26 again for a while.
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #18 from Victor Engmark ---
https://dev.exiv2.org/issues/1347#note-11
> Please ask the DigiKam Engineers to reproduce your issue with the eviv2
> command-line program and your issue will be investigated.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #17 from Maik Qualmann ---
It crashes at exactly this point with the test image "_MG_5144_v1.TIFF":
https://cgit.kde.org/digikam.git/tree/core/libs/dmetadata/metaengine.cpp#n292
Since it is not always reproducible, but under stress
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #16 from caulier.gil...@gmail.com ---
Exiv2 team is serious ? The crash backtrace is clear :
#0 0x7fec1165e186 in Exiv2::IptcData::printStructure(std::ostream&,
unsigned char const*, unsigned long, unsigned int) () from
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #15 from Victor Engmark ---
I have reported this to the Exiv2 project at https://dev.exiv2.org/issues/1347
and they say it's not an Exiv2 issue.
When I run `exiv2 [offending file]` the first line printed is
> Warning: Directory Image3,
https://bugs.kde.org/show_bug.cgi?id=393635
Maik Qualmann changed:
What|Removed |Added
CC||gd...@qswarm.com
--- Comment #14 from Maik
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #13 from caulier.gil...@gmail.com ---
But a stand alone exiv2 session will run in a process which will not share the
memory to another one as digiKam.
Or Exiv2 use a system mecanism which is badly managed, as mmap and munmap to
speed up
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #12 from Maik Qualmann ---
I think it's related to the memory contents, whether it crashes.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #11 from caulier.gil...@gmail.com ---
Well, if it's always reproducible, i don't understand why...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #10 from Maik Qualmann ---
Maybe an interesting observation here, if I open the image with the CLI exiv2
tool before, digiKam will not crash anymore.
Maik
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #9 from caulier.gil...@gmail.com ---
and typically, the Exiv2 interface written in digiKam core catch all Exiv2 C++
exceptions. So it's clear that in this case, Exiv2 do not generate a dedicated
exception and crash.
To resume, Exiv2
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #7 from caulier.gil...@gmail.com ---
*** Bug 387515 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #6 from Victor Engmark ---
(In reply to Maik Qualmann from comment #5)
> I could not reproduce the crash in Bug 387515 with the test image. Can you
> also provide this image? It would be nice if they tried to
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #5 from Maik Qualmann ---
I could not reproduce the crash in Bug 387515 with the test image. Can you also
provide this image? It would be nice if they tried to reproduce the crash with
the AppImage from
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #4 from Victor Engmark ---
Reported as https://dev.exiv2.org/issues/1347
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393635
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #2 from Victor Engmark ---
I use Exiv2 0.26.
PS: This happens with about one in ten images that I edit. It has happened at
least once in every release for the last few months. Usually DigiKam crashes
upon loading
https://bugs.kde.org/show_bug.cgi?id=393635
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|ImageEditor |Metadata-Engine
CC|
29 matches
Mail list logo