After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 434025 - warn before opening a very large image file
warn before opening a very large image file
Product: GIMP
Classification: Other
Component: Plugins
git master
Other All
: Low enhancement
: ---
Assigned To: GIMP Bugs
: 380028 (view as bug list)
Depends on: 139354
Reported: 2007-04-28 04:11 UTC by Ari Pollak
Modified: 2018-05-24 12:11 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Ari Pollak 2007-04-28 04:11:28 UTC
From Debian bug report

When opening a very large file (e.g., GIMP will most likely try to create a very large swap file at once, which will usually make the user's desktop unresponsive for a while. The max-new-image-size setting only seems to affect scaling & new images, but not opening existing images.

Surely it should be possible to guesstimate whether a given file will exceeed max-new-image-size? Especially since the size of the file itself will generally be smaller than the amount of memory it will use when opened, depending on the format.
Comment 1 Sven Neumann 2007-04-28 09:43:45 UTC
Hmm, not sure if that's desirable at all. It would definitely be difficult to implement as it would require substantial changes to the file plug-in API. I suggest closing as WONTFIX.
Comment 2 Sven Neumann 2007-05-03 13:55:33 UTC
The only reasonable way to implement this with the given plug-in API seems to be to implement it in each of the file plug-ins. I don't see how it could be done without touching every file plug-in.
Comment 3 Sven Neumann 2007-05-07 14:02:13 UTC
*** Bug 380028 has been marked as a duplicate of this bug. ***
Comment 4 Raphaël Quinet 2007-05-08 18:29:05 UTC
It may require touching every file plug-in, but it is an interesting improvement anyway.  Just looking at file size is not enough to allow the user to guess if the decompressed image (+ undo, projection and so on) will nicely fit in memory or if it will blow up the system.  The comments in the Debian bug report are rather valid.

It may be wise to delay this change until the some parts of the new plug-in/PDB API are in place, though.  Most plug-ins would have to be modified anyway, and we could think about adding a specific trigger for the image size.  So maybe we could add this to the tracking bug #101604?
Comment 5 Sven Neumann 2008-01-15 13:58:38 UTC
Changing version to "Current SVN" as this request is not specific to any
particular version.
Comment 6 GNOME Infrastructure Team 2018-05-24 12:11:51 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: