https://bugs.kde.org/show_bug.cgi?id=411214
maderios changed:
What|Removed |Added
Version|6.3.0 |6.4.0
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #59 from maderios ---
I compiled digikam from last git master today (Commit 806bcd39)
When I try to update finger prints, I get computer freeze.
Digikam himself eats about 3700M
IM7 creates 3 huge files in /tmp
magick-1828x 1247M
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #58 from maderios ---
As i wrote here https://bugs.kde.org/show_bug.cgi?id=411214#c44
issue comes from Imagemagick 6 and 7, not from Digikam itself. And yet,
strangely, this bug does not appear with the Digikam Appimage 6.3 beta
version...
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #57 from maderios ---
Rectification : compiled with IM 6
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #56 from maderios ---
Only modified huge xcf cause problem when updating folder.
I reproduced it this morning with same Digikam version (compiled with IM this
way:
Open TestModif-resized-197808-3200-1-.xcf in Gimp to resize it
image ->
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #55 from Maik Qualmann ---
Strange, I can not reproduce here that ImageMagick creates any files in the tmp
directory.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #54 from maderios ---
I forgot: freeze stops because Digikam crashes
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #53 from maderios ---
I modified big xcf file then updated folder. I get freeze during about 5
minutes.
Huge files were created in /tmp with same time:
│ magick-3060RirJ85e9piIh │ 2287M│
│ magick-3060Ru0G0fKDRxWo
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #52 from Maik Qualmann ---
ImageMagick has an exception, because it does not get the required memory. You
write in your 1st comment that the tmp file system is full. Can you reproduce
it and see which files are created there?
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #51 from maderios ---
> I get nearly same freeze with Digikam git master compiled with Imagemagick
> 6.9.10.62.
> Same errors than Appimage with xcf files, but Digikam Appimage 6.3 doesn't
> freeze computer. Problem is freeze, not errors.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #50 from maderios ---
I get nearly same freeze with Digikam git master compiled with Imagemagick
6.9.10.62.
Same errors than Appimage with xcf files, but Digikam Appimage 6.3 doesn't
freeze computer. Problem is freeze, not errors.
--
You
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #49 from maderios ---
You use Imagemagick 6.9. It's different, i understand...
For me, on Arch, I think I have to replace 'Imagemagick" by 'libmagick6' in
dependencies
https://www.archlinux.org/packages/extra/x86_64/libmagick6/
You could
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #48 from caulier.gil...@gmail.com ---
by IM version, i want mean stable version released, not git/master
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #47 from caulier.gil...@gmail.com ---
Go to Help/components Info for details in DK...
Do you suggest to compile the AppImage with a more recent version of IM ? If
yes which one ?
Gilles Caulier
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #46 from maderios ---
I compiled and install this IM git version, same freeze.
https://aur.archlinux.org/packages/imagemagick-full/
I think Digikam Appimage is built with old Imagemagick version.
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #45 from maderios ---
Rectification: i'll compile other IM git version
https://aur.archlinux.org/packages/imagemagick-full/
https://aur.archlinux.org/packages/imagemagick-git/
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #44 from maderios ---
I tried to open same file with imagemagick 7.0.8.62 (installed version on my
system):
'display TestModif-resized-197808-3200-1-.xcf'
It displays nothing, it freezes desktop and computer, it eats about 2 Go. I
have to
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #43 from maderios ---
linux-lts 4.19.68
Archlinux system
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #42 from Maik Qualmann ---
The AppImage does not load any XCF files at the moment, no large memory block
is requested, therefore no freeze. Which kernel version does your Linux system
have?
Maik
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #41 from maderios ---
It is strange that Digikam appimage doesn't freeze my computer with these
files.
Appimage is compiled with which Imagemagick version?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #40 from Maik Qualmann ---
Thanks for the test pictures. These are similar to what I already tested. My
computer is older, 2 cores and 8GB RAM. Yes, the loading with ImageMagick
consumes a lot of memory, up to 6GB and slow. But no memory
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #39 from maderios ---
> Bear in mind that such images yield a huge amount of data as bitplanes,
> several layers, etc. The ImageMagick loader needs here to load my XCF image
> up to 4.5GB. The image buffer is about 350MB at the end. The
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #38 from Maik Qualmann ---
Bear in mind that such images yield a huge amount of data as bitplanes, several
layers, etc. The ImageMagick loader needs here to load my XCF image up to
4.5GB. The image buffer is about 350MB at the end. The
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #37 from maderios ---
Precisions about these two files:
28096 x 3328 pixels
3200 x 3200 ppi
8 bit
32280 x 3824 pixels
3200 x 3200 ppi
8 bit
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #36 from maderios ---
I can send you two modified original files that cause memory issue with
Digikam.
I'm not used to Dropbox (i just created account) I think I need email receiver.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #35 from maderios ---
I just rebuilt Digikam from git master commit 58c0b5f4 'sh => bash
Gilles Caulier authored 6 hours ago'
I got some errors and freeze after launching when Digikam try to search for
new items. Digikam freezes desktop
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #34 from caulier.gil...@gmail.com ---
Git commit 689e79e0c59aee864ed282857b629d8f9c8ae9d9 by Gilles Caulier.
Committed on 27/08/2019 at 07:20.
Pushed by cgilles into branch 'master'.
enable IM large file support
M +0-1
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #33 from caulier.gil...@gmail.com ---
A missing codec in IM. Which one.
I customized the IM build with this options :
https://invent.kde.org/kde/digikam/blob/master/project/bundles/3rdparty/ext_imagemagick/CMakeLists.txt#L16
As you can
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #32 from Maik Qualmann ---
My native digiKam version can load the large XCF image created by me. The
current AppImage has an exception because of missing decoder.
Digikam::MagickLoader::load: Try to load image with ImageMagick codecs
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #31 from caulier.gil...@gmail.com ---
Maik,
I will take a look tomorrow morning.
But a simple question. Can display IM CLI tool is able to run without to crash
when you try to open this huge XCF file ?
If there is one exception caught and
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #30 from Maik Qualmann ---
Your ImageMagick version is the same as mine. The native output of comment 27
is not yet the current git/master version. There, the ImageMagick loader still
loads everything in 16 bit, which means a huge memory
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #29 from maderios ---
Good news. This issue doesn't happen with Appimage 6.3
I get errors but computer is not frozen.
I don't understand why my Digikam git version can't do the same...
^[[34mDigikam::ActionThreadBase::cancel^[[0m: Cancel
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #28 from maderios ---
Rectification:
Not 'Gimp 2.12' but 'Gimp 2.10.12' !
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #27 from maderios ---
Digikam seems have problem with big size XCF files.
Test example:
Take any image about 4600x3800
Open it in Gimp-2.12 and convert it to testxcf.xcf
File size for me: 49.6MB
Add layer background color black
Image has
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #26 from maderios ---
I use my native configuration with 127.0.0.1 now, it works. But, if you say
'localhost' is faster, I go back to it...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #25 from Maik Qualmann ---
Note: to test the AppImage the "127.0.0.1" is good. If you use your native
digiKam version, you should use "localhost" again. Depending on the server
configuration, "localhost" uses a socket file for
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #24 from maderios ---
I changed localhost -> 127.0.0.1
Appimage works now
> Would it be possible to provide such a problematic XCF file to test it here?
I can't send present problematic XCF file but, when i'll get time, i'll create
others
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #23 from Maik Qualmann ---
The problem with connecting to a MySQL server is known. The use of "localhost"
as a server address is not possible with the AppImage. You would have to use
"127.0.0.1".
Would it be possible to provide such a
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #22 from maderios ---
@Maik
I removed 4 xcf files with problem (see above), then, i could successfully
update finger prints.
I have many other xcf files but these 4 xcf files cause a problem. They are big
files, about 88 Mo each.
May be
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #21 from maderios ---
Git master, sure. I compiled it on last August 24
Archlinux system
Imagemagick installed version is 7.0.8.62, it may be different from yours?
Here is my Arch Aur modified script to clone git and build Digikam:
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #20 from Maik Qualmann ---
After deeper debugging, I can not reproduce a memory hole with XCF files and
our ImageMagick loader here. Is this behavior to reproduce for you with the
current git/master version?
Maik
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #19 from Maik Qualmann ---
Git commit 73b6b00b5a29eb064292c292d18e8a1d0441a1c1 by Maik Qualmann.
Committed on 25/08/2019 at 11:15.
Pushed by mqualmann into branch 'master'.
load image in real bit depth with the ImageMagick loader
M +10
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #18 from caulier.gil...@gmail.com ---
AppImage problem fixed. New 64 bits version is online. Please try again.
https://files.kde.org/digikam/
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #17 from caulier.gil...@gmail.com ---
No. Qt 5.11 is included in AppImage bundle as well.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #16 from maderios ---
> What is your ImageMagick version?
>
Could my Imagemagick version (7.0.8.59) be too recent?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #15 from maderios ---
Digikam Appimage doesnt work on my system. It needs old QT5 11.
My QT5 is 5.13.0-7
In console:
-- digiKam Linux AppImage Bundle
-- Use 'help' as CLI argument to know all available options for digiKam
application.
--
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #14 from maderios ---
Great. Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #13 from caulier.gil...@gmail.com ---
Just look on top level directory :
https://files.kde.org/digikam/
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #12 from maderios ---
imagemagick 7.0.8.59-1 is installed
@gilles I could try Appimage but I don't see any md5 or sha256 in your link...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #11 from caulier.gil...@gmail.com ---
And didi you reproduce the dysfunction with last 6.3.0 AppImage pre-release
bundle just uploaded ?
https://files.kde.org/digikam/digikam-6.3.0-git-20190824T081330-x86-64.appimage.mirrorlist
Gilles
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #10 from Maik Qualmann ---
What is your ImageMagick version?
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #9 from caulier.gil...@gmail.com ---
No. ImageMagick run time deps, as with convert CLI tool for ex.
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
Maik Qualmann changed:
What|Removed |Added
Version Fixed In|6.3.0 |
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #8 from maderios ---
Run-time Exiv dependencies?
Installed on my computer:
exiv2 0.27.2-1
libgexiv2 0.12.0-2
libexif 0.6.21-3
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #6 from maderios ---
Maybe useful:
errors with "file contains data of an unknown image type" are big .xcf files,
about 86 Mo
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #5 from maderios ---
(In reply to Maik Qualmann from comment #2)
> Ahh, I also see that your tmp is running full. This is due to the
> KImageFormat packet. it contains a broken ImageMagick Loader that generates
> this tmp data. As a
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #4 from Maik Qualmann ---
Note: compile digiKam with ImageMagick support. We have our own ImageMagick
loader to support additional image formats. Although only the first layer is
loaded with new Gimp XCF files, but you know that.
Maik
--
https://bugs.kde.org/show_bug.cgi?id=411214
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=411214
--- Comment #2 from Maik Qualmann ---
Ahh, I also see that your tmp is running full. This is due to the KImageFormat
packet. it contains a broken ImageMagick Loader that generates this tmp data.
As a workaround, remove this KImageFormat package and
https://bugs.kde.org/show_bug.cgi?id=411214
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
https://bugs.kde.org/show_bug.cgi?id=411214
maderios changed:
What|Removed |Added
Summary|Digikam git beta 3 eats |Digikam git beta 6.3 eats
|huge
62 matches
Mail list logo
