https://bugs.kde.org/show_bug.cgi?id=421043
Maik Qualmann changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #28 from Maik Qualmann ---
Thank you for testing and your feedback.
I was pretty sure now that the problem was fixed. ((:-))
We subjected the image loader to a review and code optimization, which was
definitely good.
In the end, it was just
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #27 from Cliff Albert ---
(In reply to Cliff Albert from comment #26)
> (In reply to Maik Qualmann from comment #25)
> > A new version of the AppImage that contains the latest patches is available.
> > Can you please test whether the
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #26 from Cliff Albert ---
(In reply to Maik Qualmann from comment #25)
> A new version of the AppImage that contains the latest patches is available.
> Can you please test whether the problem still exists?
>
> Maik
Looks good, normally it
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #25 from Maik Qualmann ---
A new version of the AppImage that contains the latest patches is available.
Can you please test whether the problem still exists?
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #24 from Maik Qualmann ---
Git commit 46d4abd0cfcbdbdbab1f1189186e1737caec2839 by Maik Qualmann.
Committed on 14/01/2021 at 06:49.
Pushed by mqualmann into branch 'master'.
call wait() after stop() before call start() again
Otherwise a
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #23 from Maik Qualmann ---
Git commit d62937a9e0c3a496f8ccbdbe72835d08899d6718 by Maik Qualmann.
Committed on 14/01/2021 at 06:33.
Pushed by mqualmann into branch 'master'.
the DynamicThread should not be a QRunnable
Otherwise it is a bit
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #22 from Cliff Albert ---
Is this patch already in digiKam-7.2.0-rc-20210112T182159-x86-64-debug.appimage
?
Because it just crashed again (Maintenance -> Face Recognition with "clear
unconfirmed results and scan again" on):
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #21 from Maik Qualmann ---
Git commit df6e4fcf0157246f6d1d646f6d768d2b27e48f89 by Maik Qualmann.
Committed on 05/01/2021 at 11:42.
Pushed by mqualmann into branch 'master'.
this could be a cause of the crash in the preview loader
Related:
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #20 from Cliff Albert ---
It has been a while, but i've hit the same issue again.
Release: digikam-7.2.0-rc-20210103T180117-x86-64-debug.appimage
This time the issue does not appear during normal face detection / face
recognition. But
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #19 from Maik Qualmann ---
Git commit cdef325da3796effb0699ed9654d58c20eda7108 by Maik Qualmann.
Committed on 26/10/2020 at 11:35.
Pushed by mqualmann into branch 'master'.
add extra debug
M +2-0
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #18 from Cliff Albert ---
Here is another backtrace. This one has been made with
digikam-7.2.0-beta1-20201025T154101-x86-64-debug.appimage
The machine i'm using has been updated to Ubuntu 20.10:
Linux porkstation 5.8.0-25-generic
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #17 from Maik Qualmann ---
Git commit 4cf9c413ee1834b9c199f5e762a8fca5b3f46c5e by Maik Qualmann.
Committed on 20/10/2020 at 05:52.
Pushed by mqualmann into branch 'master'.
only for a test protect jpeg loader with a mutex
M +4-0
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #16 from Maik Qualmann ---
The libjpeg is not 100% thread safe, at least the error handling can lead to a
crash. Tonight I will test the DImg Jpeg loader with a mutex.
Maik
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #15 from Cliff Albert ---
I don't know if the patch already made it to
digikam-7.2.0-beta1-20201016T092735-x86-64-debug.appimage, but here is another
slightly different backtrace:
Thread 29 "Thread (pooled)" received signal SIGSEGV,
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #14 from Maik Qualmann ---
Git commit d37b969a2fcd09ce97707c48c5c23730d97e069c by Maik Qualmann.
Committed on 15/10/2020 at 17:12.
Pushed by mqualmann into branch 'master'.
this bug after the code revert could be the problem
M +1-1
https://bugs.kde.org/show_bug.cgi?id=421043
Cliff Albert changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=421043
caulier.gil...@gmail.com changed:
What|Removed |Added
Summary|Faces Detection crashes |Faces Detection crashes
https://bugs.kde.org/show_bug.cgi?id=421043
caulier.gil...@gmail.com changed:
What|Removed |Added
Resolution|--- |FIXED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #11 from Cliff Albert ---
After testing for 2 days I haven't encountered the problem.
I'll do some more this weekend. But so far it's all good.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #10 from caulier.gil...@gmail.com ---
Hi,
Can you check if this crash still exist with last weekly AppImage build
available here :
https://files.kde.org/digikam/
Thanks in advance
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=421043
Maik Qualmann changed:
What|Removed |Added
CC||paazm...@yahoo.com
--- Comment #9 from Maik
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #8 from Maik Qualmann ---
Git commit b66eb0a0556388fc532fcc5bba7a40ed6eda2fc1 by Maik Qualmann.
Committed on 12/07/2020 at 06:58.
Pushed by mqualmann into branch 'master'.
disable OpenCL for everyone
An analysis with Heaptrack shows that
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #7 from Maik Qualmann ---
Git commit 880b4c0faa511364135deed61e68e031b8ddfe2e by Maik Qualmann.
Committed on 14/06/2020 at 09:32.
Pushed by mqualmann into branch 'master'.
do not use static for this DImg function
Related: bug 422735, bug
https://bugs.kde.org/show_bug.cgi?id=421043
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=421043
Chris Weyland changed:
What|Removed |Added
CC||kdeb...@nextmail.cc
--- Comment #5 from Chris
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #4 from Maik Qualmann ---
As I said, these crashes are very strange. We only watch them on Ubuntu based
distributions related to Intel Core 5 or 7.
This message would only appear if there was a code error, under normal
circumstances it can
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #3 from Cliff Albert ---
Upgraded to Ubuntu 20.04 LTS (with kernel Linux porkstation 5.4.0-29-generic
#33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux)
The following error appears after which a segfault occurs:
https://bugs.kde.org/show_bug.cgi?id=421043
--- Comment #2 from Cliff Albert ---
No this is a Xeon X5670 (6 core 2.93Ghz), from the Gulfton/Westmere EP
architecture.
Equivalent to the Core i7 970-990 series.
I indeed read some bug reports concerning the Core i5 having something to do
with the
https://bugs.kde.org/show_bug.cgi?id=421043
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
30 matches
Mail list logo
