eog (Ubuntu image viewer) consumes all memory when opening a tiff file

Bug #1828720 reported by Ben Weiner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdk-pixbuf
New
Unknown
gdk-pixbuf (Ubuntu)
Triaged
High
Unassigned

Bug Description

The ImageViewer app (/usr/bin/eog) will go into a loop if a TIFF files are opened. Any TIFF file can cause a loop even if less than 1MB in size, so it seems that the program is encountering an internal issue with the TIFF format.

The loop quickly consumes all free memory and locks up the machine (I do not have any swap).

Steps to reproduce:
* open any TIFF file using ImageViewer, the default image file handler.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: eog 3.28.1-1
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 12 11:11:02 2019
InstallationDate: Installed on 2015-02-21 (1540 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: eog
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Ben Weiner (ben-chgta) wrote :
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. Could you add a file example to the bug?

Changed in eog (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Ben Weiner (ben-chgta) wrote :

This file is identical in pixel dimensions to one that caused the bug earlier. It is 1-bit with a size of 10332px x 4148px. It is LZW compressed and contains an entirely white image.

*Opening this file with Image Viewer (eog) doesn't trigger the bug* with the resources available on my system now, though it takes a bit of time to appear and requires over 1GB of memory. I will load up more software and see if that affects the outcome, and I will try the one of the files that did trigger it earlier at the current system usage level (I cannot upload that as it's a private scan from a book and sharing it would violate copyright).

Revision history for this message
Ben Weiner (ben-chgta) wrote :

OK the original trigger file is OK now and uses a similar amount of memory to load.

I guess it would be more appropriate to say that there's nothing to stop eog loading a file that's impracticably large, and a refinement would be to do a rough calculation of the memory requirement and ask the user to confirm they want to open it.

Revision history for this message
Ben Weiner (ben-chgta) wrote :

OK well with more resources in use the behaviour I am getting is that Image Viewer boots, shows a blank window, and then exits. So that's a little bit like my comment #4.

Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in eog (Ubuntu):
status: Incomplete → New
affects: eog (Ubuntu) → gdk-pixbuf (Ubuntu)
Changed in gdk-pixbuf (Ubuntu):
status: New → Triaged
Changed in gdk-pixbuf:
status: Unknown → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.