https://bugs.kde.org/show_bug.cgi?id=427056
--- Comment #14 from Maik Qualmann ---
Git commit 6d3365d72054253d73c8aac223f91081415166f2 by Maik Qualmann.
Committed on 28/09/2020 at 18:42.
Pushed by mqualmann into branch 'master'.
use quintptr to prevent 64 arithmetic on 32 bit platforms
M +2
https://bugs.kde.org/show_bug.cgi?id=427056
--- Comment #13 from Maik Qualmann ---
Yes, quintptr is a good indication. In the function for memory allocation it is
checked whether it is possible for the architecture. Here in the PNG loader,
too, the function would have been exited under 32 bit
https://bugs.kde.org/show_bug.cgi?id=427056
--- Comment #12 from Christoph Feck ---
Are 32 bit systems still supported for digikam? If yes, it might make sense to
1) use quintptr to not force 64 bit arithmetic on 32 bit systems
2) add a range check and error out properly instead of blindly
https://bugs.kde.org/show_bug.cgi?id=427056
Maik Qualmann changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/grap
https://bugs.kde.org/show_bug.cgi?id=427056
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=427056
--- Comment #9 from caulier.gil...@gmail.com ---
If it do not crash in ImageMagick, it must not crash in digiKam PNG plugin.
Both use libpng, so the behavior must be the same.
Thanks to share the PNG file, this will help to investigate.
Gilles Caulier
https://bugs.kde.org/show_bug.cgi?id=427056
--- Comment #8 from Brad Templeton ---
The upload is now complete at http://www.templetons.com/etc/big4.png
if you really want to test on the actual file.
Note that while catching exceptions in the plugin is a good idea to avoid
segfault of all of
https://bugs.kde.org/show_bug.cgi?id=427056
--- Comment #7 from Brad Templeton ---
BTW, display doesn't crash, just displays a full sized gray window but it does
show a little thumbnail of it.
If you want to work with it and have the bandwidth, it will be uploaded to
https://bugs.kde.org/show_bug.cgi?id=427056
--- Comment #6 from Brad Templeton ---
Correct. It is a near-gigapixel panorama. I have hundreds of these and most
don't cause a problem, though I usually have them as tiff or when they fit, jpg
If it is too large for digikam, that is
https://bugs.kde.org/show_bug.cgi?id=427056
--- Comment #5 from caulier.gil...@gmail.com ---
The crash is located in libpng at end. It pass in thumbnail engine, and in DImg
plugin to load PNG file, and finaly libpng.
This is can be due of digiKam DImg plugin to handle memory with libpng, or the
https://bugs.kde.org/show_bug.cgi?id=427056
--- Comment #4 from caulier.gil...@gmail.com ---
Thanks for the feedback.
It's a huge image. How did you generate this file ? Panorama ? It's a landscape
? It's a astro photo ?
Can you open the file in ImageMagik "display" command line tool ?
Gilles
https://bugs.kde.org/show_bug.cgi?id=427056
--- Comment #3 from Brad Templeton ---
Let me add I do have a very fast internet connection, so if you really want the
gigabyte file, I can make it available for you -- I just figured you might want
to look for something obvious at the designated point
https://bugs.kde.org/show_bug.cgi?id=427056
--- Comment #2 from Brad Templeton ---
Image: big4.png
Format: PNG (Portable Network Graphics)
Mime type: image/png
Class: DirectClass
Geometry: 49494x15588+0+0
Units: Undefined
Colorspace: sRGB
Type: TrueColor
Base type: Undefined
https://bugs.kde.org/show_bug.cgi?id=427056
--- Comment #1 from caulier.gil...@gmail.com ---
Can you give us the ouput of ImageMagick tool "identify" with this PNG file.
The command line is "idenify -v _foo_.png"
Best regards
Gilles Caulier
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=427056
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|Thumbs-Image|Plugin-FilesIO-PNG
15 matches
Mail list logo
