• ulterno@programming.devEnglish
        2·
        4 days ago

        Hmm, but that shouldn’t end up taking that much space either, no?
        Does it really crash by filling up the RAM?

        I’d expect there to be other reasons for it.
        Though I haven’t used it enough to get a long undo history <- as a potential reason for me to not have experienced the crash.

        • bleistift2@sopuli.xyzOPEnglish
          2·
          3 days ago

          Hmm, but that shouldn’t end up taking that much space either, no?

          I can confirm that it indeed uses little RAM.

          I was wrangling lots of big images and noticed that RAM usage was increasing steadily. Though that only seems to happen when generating new layers (e.g. by combinding them). Moving, for instance, does nothing. However I just noticed that doing things like adjusting the contrast (using the values histogram tool, sorry don’t know its English name) or adjusting the color temperature adds 300–400MBs. Do each operation three times on 9–12 images and you have a deadly amount of RAM usage.

            • bleistift2@sopuli.xyzOPEnglish
              1·
              3 days ago

              Personally, I would be fine if GIMP had just said, “too many operations, shrinking Undo history” or something like that. No amount of optimization gets rid of this issue. At some point, the machine’s resources are just exhausted.

              • ulterno@programming.devEnglish
                1·
                3 days ago

                Konsole has the option to set scrollback line count and an alternative “infinite” where it just writes to a file on disk.
                GIMP can also have that and can ask for which disk it wants you to use, so if you have a 20TB HDD to dedicate for that, might as well.

                In this case, the most recent 10 or so remain in RAM, while others only have a reference to it, in RAM.