2GB limit on Resource Consumption: Tile cache size
This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.
This is a read-only list on gimpusers.com so this discussion thread is read-only, too.
2GB limit on Resource Consumption: Tile cache size | Elle Stone | 17 Sep 18:23 |
2GB limit on Resource Consumption: Tile cache size | Liam R E Quin | 18 Sep 01:32 |
2GB limit on Resource Consumption: Tile cache size | Elle Stone | 18 Sep 12:15 |
2GB limit on Resource Consumption: Tile cache size | Tobias Jakobs | 18 Sep 13:35 |
2GB limit on Resource Consumption: Tile cache size | Michael Natterer | 18 Sep 18:08 |
2GB limit on Resource Consumption: Tile cache size | Elle Stone | 19 Sep 19:11 |
2GB limit on Resource Consumption: Tile cache size | Jon Nordby | 18 Sep 14:08 |
2GB limit on Resource Consumption: Tile cache size
While making changes to "Edit/Preferences/Environment, Resource Consumption: Tile cache size", I noticed a warning when I tried to increase the cache size to 2 gigabytes, or 2048 megabytes (terminal output, Gimp 2.9, started from the command line):
(gimp-2.9:3518): GLib-GObject-WARNING **: value "-2147483648" of type `gint' is invalid or out of range for property `cache-size' of type `gint'
If I set the cache size to 2047 megabytes, there is no warning. If I set the cache size to more than 2048 megabytes, the 'GLib-GObject-WARNING **: value' gets correspondingly larger.
I only have 4 GB of ram on my computer, but I have successfully given more than 2GB to other image editing programs. A lot of people have computers with way more than 4GB of ram. Would it make any practical difference to be able to use more than 2GB of ram for the tile cache when using Gimp? It seems odd to be limited to less than 2GB for the tile cache size, solely because the type is gint.
Kindest regards, Elle Stone
2GB limit on Resource Consumption: Tile cache size
On Mon, 2012-09-17 at 14:23 -0400, Elle Stone wrote:
While making changes to "Edit/Preferences/Environment, Resource Consumption: Tile cache size", I noticed a warning when I tried to increase the cache size to 2 gigabytes, or 2048 megabytes (terminal output, Gimp 2.9, started from the command line)
I take it that this is a 32-bit computer and 32-bit build of GIMP?
If so, yes, 2G is likely the limit. On many 32-bit Linux systems there's also a 3G process size limit.
On 64-bit systems you can set the tile cache size larger, at least on Linux systems.
Liam
2GB limit on Resource Consumption: Tile cache size
No, it is a 64-bit computer and a 64-bit build of Gimp 2.9, running Linux (OpenSuse 12.2). It's just not a very new computer and doesn't have a lot of RAM by today's standards.
I compiled Gimp using "--enable-debug" so perhaps the terminal output that I'm seeing is only available if "--enable-debug" is used.
I can easily set the tile cache size larger than 2GB using "Edit/Preferences/Environment, Resource Consumption: Tile cache size". The problem is that when starting Gimp from the command line and then setting the tile cache size to more than 2GB, I see a warning in the terminal output telling me that the maximum tile cache size has been exceeded.
The warning says that the "type" for the tile cache size is "gint", which means 2GB really is the limit. At least on my system. To check the maximum that "gint" can hold on my system, I added in a printf statement in the lcms plug-in code that I'm working on, to print out G_MAXINT, which turns out to be 2GB. See http://developer.gnome.org/glib/stable/glib-Basic-Types.html#G-MAXINT:CAPS.
As anything greater than 2GB exceeds the limit of what "gint" can hold, I don't see how setting anything greater than 2GB through "Preferences" actually gets you more than 2GB.
Elle
On 9/17/12, Liam R E Quin wrote:
On Mon, 2012-09-17 at 14:23 -0400, Elle Stone wrote:
While making changes to "Edit/Preferences/Environment, Resource Consumption: Tile cache size", I noticed a warning when I tried to increase the cache size to 2 gigabytes, or 2048 megabytes (terminal output, Gimp 2.9, started from the command line)
I take it that this is a 32-bit computer and 32-bit build of GIMP?
If so, yes, 2G is likely the limit. On many 32-bit Linux systems there's also a 3G process size limit.
On 64-bit systems you can set the tile cache size larger, at least on Linux systems.
Liam
--
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org freenode/#xml
2GB limit on Resource Consumption: Tile cache size
On Tue, Sep 18, 2012 at 2:15 PM, Elle Stone wrote:
...
The warning says that the "type" for the tile cache size is "gint", which means 2GB really is the limit. At least on my system. To check the maximum that "gint" can hold on my system, I added in a printf statement in the lcms plug-in code that I'm working on, to print out G_MAXINT, which turns out to be 2GB. See http://developer.gnome.org/glib/stable/glib-Basic-Types.html#G-MAXINT:CAPS.
As anything greater than 2GB exceeds the limit of what "gint" can hold, I don't see how setting anything greater than 2GB through "Preferences" actually gets you more than 2GB.
For me, as a not C developer, it looks like this should be changet to guint or even better guint64. But lets wait what Mitch things about this.
Regards
Tobias
2GB limit on Resource Consumption: Tile cache size
On 17 September 2012 20:23, Elle Stone wrote:
While making changes to "Edit/Preferences/Environment, Resource Consumption: Tile cache size", I noticed a warning when I tried to increase the cache size to 2 gigabytes, or 2048 megabytes (terminal output, Gimp 2.9, started from the command line):
(gimp-2.9:3518): GLib-GObject-WARNING **: value "-2147483648" of type `gint' is invalid or out of range for property `cache-size' of type `gint'
If I set the cache size to 2047 megabytes, there is no warning. If I set the cache size to more than 2048 megabytes, the 'GLib-GObject-WARNING **: value' gets correspondingly larger.
I only have 4 GB of ram on my computer, but I have successfully given more than 2GB to other image editing programs. A lot of people have computers with way more than 4GB of ram. Would it make any practical difference to be able to use more than 2GB of ram for the tile cache when using Gimp? It seems odd to be limited to less than 2GB for the tile cache size, solely because the type is gint.
It is probably this issue:
https://bugzilla.gnome.org/show_bug.cgi?id=648265
2GB limit on Resource Consumption: Tile cache size
On Tue, 2012-09-18 at 15:35 +0200, Tobias Jakobs wrote:
On Tue, Sep 18, 2012 at 2:15 PM, Elle Stone wrote:
...
The warning says that the "type" for the tile cache size is "gint", which means 2GB really is the limit. At least on my system. To check the maximum that "gint" can hold on my system, I added in a printf statement in the lcms plug-in code that I'm working on, to print out G_MAXINT, which turns out to be 2GB. See http://developer.gnome.org/glib/stable/glib-Basic-Types.html#G-MAXINT:CAPS.
As anything greater than 2GB exceeds the limit of what "gint" can hold, I don't see how setting anything greater than 2GB through "Preferences" actually gets you more than 2GB.
For me, as a not C developer, it looks like this should be changet to guint or even better guint64. But lets wait what Mitch things about this.
I think pull, the code was broken:
commit 52af6e3f3f67d37aa72d06a5f60b1a3967d6c297
Author: Michael Natterer
Date: Tue Sep 18 20:07:13 2012 +0200
app: fix the code that sets the 64bit tile cache size on GeglConfig
app/gegl/gimp-gegl.c | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-)
--mitch
2GB limit on Resource Consumption: Tile cache size
On 9/18/12, Michael Natterer wrote:
I think pull, the code was broken:
commit 52af6e3f3f67d37aa72d06a5f60b1a3967d6c297 Author: Michael Natterer
Date: Tue Sep 18 20:07:13 2012 +0200app: fix the code that sets the 64bit tile cache size on GeglConfig
app/gegl/gimp-gegl.c | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-)
--mitch
I did git pull and recompiled Gimp. The terminal output no longer complains when setting Preferences/Environment/Resource Consumption/Tile cache size greater than 2GB. Thank you, Mitch!
Elle