On 2/5/19 5:35 PM, jEsuSdA 8) wrote:
El 2/2/19 a las 9:58, Ofnuts escribió:
The fact that the memory isn't marked free doesn't mean it is
unusable. Tried in Gimp 2.10 on Ubuntu:
- load 5 20MPx Jpegs: memory is 1.35GB
- close all: memory still at 1.35GB
- load them again: memory is 1.4GB
- c
Does GIMP clear undo memory associated with images that have been closed
(without closing GIMP)?
Thanks for the great answers, everyone. I'm learning a lot about GIMP
memory management here!
-C
On Wed, Feb 6, 2019 at 9:14 AM Ofnuts wrote:
> On 2/5/19 5:35 PM, jEsuSdA 8) wrote:
> > El 2/2/19 a l
On Wed, 6 Feb 2019 11:14:21 +0200, Ofnuts wrote:
> On 2/5/19 5:35 PM, jEsuSdA 8) wrote:
>> El 2/2/19 a las 9:58, Ofnuts escribió:
>>> The fact that the memory isn't marked free doesn't mean it is
>>> unusable. Tried in Gimp 2.10 on Ubuntu:
>>>
>>> - load 5 20MPx Jpegs: memory is 1.35GB
>>>
>>> - c
I think you should open a bug report:
https://www.gimp.org/bugs/
Robert Krawitz escreveu no dia quarta, 6/02/2019 à(s) 13:34:
>
> On Wed, 6 Feb 2019 11:14:21 +0200, Ofnuts wrote:
> > On 2/5/19 5:35 PM, jEsuSdA 8) wrote:
> >> El 2/2/19 a las 9:58, Ofnuts escribió:
> >>> The fact that the memory is
Øyvind Kolås wrote:
> If you need to restrict the amount of memory GIMP is permitted to use
> (before swapping tiles of the image out to disk and being slower) you
> should adjust the tile-cache-size in GIMP's preferences.
Well, you do want GIMP to use the memory if it needs it.
> Apart from mem
On Wed, 2019-02-06 at 18:23 +0100, Peter Suetterlin wrote:
> By design allocators tend
> > to
> > keep freed memory around for reuse in future allocation calls,
>
> But this is not very social to other programs running on the same
> machine, is
> it? I have noticed this behavior of GIMP myself be
