https://bugs.kde.org/show_bug.cgi?id=405232
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In||6.4.0
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #35 from caulier.gil...@gmail.com ---
About presentation and low resolution image on monitor, look in digiKam
Views/Preview if full image is used to render preview on screen.
Best
Gilles Caulier
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #34 from harald.a...@web.de ---
Hi there,
I have a new machine now, 64bit Win10 Pro, and have installed digiKam 6.3.0. I
have not observed any crashes or blank pages in Slide Show or Presentation
anymore :-) Unfortunately, I won't be able to
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #33 from Maik Qualmann ---
Check out this comment for a link to a recent GIT version of digiKam-6.2.0 on
my GDrive:
https://bugs.kde.org/show_bug.cgi?id=408471#c7
Maik
--
You are receiving this mail because:
You are watching all bug cha
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #32 from Maik Qualmann ---
Git commit dac492a5b7423ffc91eaa7cade358bf9aa685a54 by Maik Qualmann.
Committed on 16/06/2019 at 08:24.
Pushed by mqualmann into branch 'master'.
check after allocating memory only for null pointer on Windows
Rela
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #31 from Maik Qualmann ---
Yes, at the moment I have no idea why the memory allocation fails. We use a C++
function Type* reserved = new Type[size] (Type can be unsigned char*). After
the digiKam-6.1.0 release I will test it with the C funct
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #30 from harald.a...@web.de ---
Maik,
I understand that you cannot fix a problem that doesn't show up in your setup.
So I guess I'll have to leave it at that.
Should you have any further idea, or if you would like me to try or verify
anythi
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #29 from Maik Qualmann ---
I take this from the LOG:
digikam.dimg: Failed to allocate chunk of memory of size 64131072
std::bad_alloc
digikam.dimg.jpeg: Cannot allocate memory!
Reserving around 61 MB of memory for the image buffer
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #28 from harald.a...@web.de ---
Created attachment 119121
--> https://bugs.kde.org/attachment.cgi?id=119121&action=edit
digiKAm crash log from Presentation without OpenGL transition
Regarding Presentation, basically the same behavior as be
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #27 from harald.a...@web.de ---
Given that the log again indicates memory allocation problems but it is clear
to me that my machine is not the problem (more than 1 GB free at time of
running this): Might it be possible that there is some rest
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #26 from harald.a...@web.de ---
Created attachment 119119
--> https://bugs.kde.org/attachment.cgi?id=119119&action=edit
Slideshow log
Mike,
from March 15 onwards, I had used version
digiKam-6.1.0-git-20190315T074305-Win32.exe. Before that
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #25 from Maik Qualmann ---
Are you really using the last available Windows version of digiKam? I do not
think so, because the video player should not appear in the crash log, because
in a faulty image load only with GIF images of the video p
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #24 from harald.a...@web.de ---
Created attachment 119079
--> https://bugs.kde.org/attachment.cgi?id=119079&action=edit
Crash log
In the second crash, however, the message was not displayed, and a crash log
entry was created. See attached.
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #23 from harald.a...@web.de ---
Created attachment 119078
--> https://bugs.kde.org/attachment.cgi?id=119078&action=edit
Crash message
Something else I noticed:
Most of the time (I'd say at least 19 out of 20) when digiKam crashes, it
disp
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #22 from harald.a...@web.de ---
Created attachment 119077
--> https://bugs.kde.org/attachment.cgi?id=119077&action=edit
digiKam and 20 instances of IrfanView
Maik,
So I'm not going to give up easily...
Just to show that the problem *cann
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #21 from harald.a...@web.de ---
(In reply to Maik Qualmann from comment #18)
> The log of Comment 11 is not from the Presentation but from the Slideshow.
Maik,
Well, it was the log that I found at the location described by Gilles. I
couldn'
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #20 from Maik Qualmann ---
Git commit 187f53b0ef3cee38a240ca01563884e035137e1d by Maik Qualmann.
Committed on 17/03/2019 at 21:34.
Pushed by mqualmann into branch 'master'.
do not try the video loader if the image failed to load
M +2-
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #19 from Maik Qualmann ---
Git commit ede14ddcf215d0a55cf3aa84c94296e0fb9e8240 by Maik Qualmann.
Committed on 17/03/2019 at 21:30.
Pushed by mqualmann into branch 'master'.
try not to load with QImage anymore, preview thread already does it
https://bugs.kde.org/show_bug.cgi?id=405232
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #18 from Maik
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #17 from Maik Qualmann ---
Git commit 6e764908da4651eeb60d45b32cfd138b122703ca by Maik Qualmann.
Committed on 17/03/2019 at 18:59.
Pushed by mqualmann into branch 'master'.
better check for OpenGL availability
M +3-3core/dplugins/
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #16 from Maik Qualmann ---
Git commit 3353509269a647f9e4f68ae36241ff80461b45b0 by Maik Qualmann.
Committed on 17/03/2019 at 18:22.
Pushed by mqualmann into branch 'master'.
add checks if QImage is NULL
M +10 -0core/dplugins/generic/
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #15 from harald.a...@web.de ---
Gilles,
No, no video. Only jpeg files.
I saw that there were several crash reports in the log. However, I must have
crashed it at least 50 times; I don't find *that* many entries. Also, when I
delete (or rena
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #14 from caulier.gil...@gmail.com ---
The file backtrace group more than one crashes. All are concatenated.
Do you have video files to play while Slideshow ? I see plenty of crashes in
QtAV module which is used to render video on the screen.
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #13 from harald.a...@web.de ---
Created attachment 118847
--> https://bugs.kde.org/attachment.cgi?id=118847&action=edit
Crash log
Gilles,
When I let it crash today, it doesn't seem to write a crash log. However, there
is a log from yester
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #12 from harald.a...@web.de ---
Created attachment 118824
--> https://bugs.kde.org/attachment.cgi?id=118824&action=edit
Screenshot of Task Manager while running digiKam
Ok, the predictability (Slideshow always crashes after first image) I
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #11 from harald.a...@web.de ---
Created attachment 118823
--> https://bugs.kde.org/attachment.cgi?id=118823&action=edit
Log for "Presentation" with transition "None"
--
You are receiving this mail because:
You are watching all bug changes
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #9 from caulier.gil...@gmail.com ---
It's clear, there is a memory allocation error :
digikam.dimg: Failed to allocate chunk of memory of size 64131072
std::bad_alloc
Do you found the crash backtrace file ?
Gilles Caulier
--
You
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #10 from harald.a...@web.de ---
Created attachment 118822
--> https://bugs.kde.org/attachment.cgi?id=118822&action=edit
Log for "Presentation" with OpenGL transition
Behavior was different from the one described before. It did not show jus
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #8 from harald.a...@web.de ---
Created attachment 118821
--> https://bugs.kde.org/attachment.cgi?id=118821&action=edit
Log for "Slideshow"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #7 from caulier.gil...@gmail.com ---
If it crash, you must see a crash backtrace file generated by DrMinGW in your
home directory :
C:\Users\_user_name_\AppData\Local\digikam_crash.log
Gilles Caulier
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #6 from harald.a...@web.de ---
Gilles,
The following is for digiKam-6.1.0-git-20190315T074305-Win32.
- No error message at startup anymore.
- Slideshow: Crashes. However, it now seems to consistently show the first
picture and crash when t
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #5 from caulier.gil...@gmail.com ---
Harald,
The 6.1.0 pre-release installer have been updated this morning. Please test and
report :
https://files.kde.org/digikam/
Gilles Caulier
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #4 from caulier.gil...@gmail.com ---
Git commit d37592eb30115e8bd196e6ef4a000ef9111d925b by Gilles Caulier.
Committed on 10/03/2019 at 18:20.
Pushed by cgilles into branch 'master'.
compile DrMinGw with MXE instead to use pre-compiled DLL
M
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #3 from caulier.gil...@gmail.com ---
This error message is due to my last DrMinGW update. I will fix it.
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405232
--- Comment #2 from harald.a...@web.de ---
Created attachment 118684
--> https://bugs.kde.org/attachment.cgi?id=118684&action=edit
6.1.0 start error message
Ok, tried that.
When starting, the attached error message shows up, but digiKam starts
noneth
https://bugs.kde.org/show_bug.cgi?id=405232
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|general |Plugin-Generic-SlideShow
--
You are
https://bugs.kde.org/show_bug.cgi?id=405232
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
37 matches
Mail list logo
