Public bug reported:

eog crashes when I try to open it on this PNG file.

    $ eog crasher.png

    (eog:19783): Gdk-ERROR **: 01:44:05.714: The program 'eog' received an X 
Window System error.
    This probably reflects a bug in the program.
    The error was 'BadAlloc (insufficient resources for operation)'.
      (Details: serial 456 error_code 11 request_code 130 (MIT-SHM) minor_code 
5)
      (Note to programmers: normally, X errors are reported asynchronously;
       that is, you will receive the error a while after causing it.
       To debug your program, run it with the GDK_SYNCHRONIZE environment
       variable to change this behavior. You can then get a meaningful
       backtrace from your debugger if you break on the gdk_x_error() function.)
    Trace/breakpoint trap (core dumped)


Probably because the image is unusually tall.

    $ file crasher.png 
    crasher.png: PNG image data, 1138 x 32768, 1-bit colormap, non-interlaced

It is, however, a valid PNG file.

    $ pnginfo crasher.png
    crasher.png...
      Image Width: 1138 Image Length: 32768
      Bitdepth (Bits/Sample): 1
      Channels (Samples/Pixel): 1
      Pixel depth (Pixel Depth): 1
      Colour Type (Photometric Interpretation): PALETTED COLOUR (1 colours, 0 
transparent) 
      Image filter: Single row per byte filter 
      Interlacing: No interlacing 
      Compression Scheme: Deflate method 8, 32k window
      Resolution: 0, 0 (unit unknown)
      FillOrder: msb-to-lsb
      Byte Order: Network (Big Endian)
      Number of text strings: 0

    $ pngcheck -v crasher.png
    File: crasher.png (4680 bytes)
      chunk IHDR at offset 0x0000c, length 13
        1138 x 32768 image, 1-bit palette, non-interlaced
      chunk PLTE at offset 0x00025, length 3: 1 palette entry
      chunk IDAT at offset 0x00034, length 4608
        zlib: deflated, 32K window, default compression
      chunk IEND at offset 0x01240, length 0
    No errors detected in crasher.png (4 chunks, 99.9% compression).

I don't have a convenient way to check a newer version of eog because of
a bug in the snap package.

https://gitlab.gnome.org/GNOME/eog/-/issues/211

Maybe related:

> bad alloc on large (but not too large) image

https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1786268

althought this file is quite small:

    $ du --bytes crasher.png 
    4680    crasher.png

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: eog 3.28.1-1
ProcVersionSignature: Ubuntu 5.4.0-87.98~18.04.1-generic 5.4.140
Uname: Linux 5.4.0-87-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.26
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Oct 12 21:30:44 2021
InstallationDate: Installed on 2020-02-01 (619 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: eog
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: eog (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to eog in Ubuntu.
https://bugs.launchpad.net/bugs/1946821

Title:
  eog crashes on tall image

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1946821/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to