(02-12-2023, 04:48 AM)rickk Wrote: For reference, just now on a fresh boot with no other applications running, I opened a 10,800 X 14,400 *.png file, 93 MB in size.
Very first operation, attempted to stroke a path 42 pixels wide, by 3600 pixels long......and *poof*...all gone!
Doubtfully a "memory depleted" scenario, and on a machine that otherwise runs stable, all day long..
And then reopened Gimp and successfully completed the very same operation, without incident. So while my experience fails the "reproducible" litmus test.... It does appear there is some "paths on large images" stability issue.
The purpose of this post is to document, not intended as a gripe, so please don't misinterpret my intent.
But there is something to this.
Asus laptop
Intel I-3 processor twin core 2.3 Ghz
8 GB Ram
64 bit Knoppix OS
32 bit Gimp
No other stability issues apparent
How much swap space have you got on the system? What is your tile cache size? I ask this because you are on the low side of RAM and modern OSes use a lazy allocation strategy: allocation requests get a positive answer, and actual allocation happens when the process actually tries to use that memory. If there is no memory available, the OS kills a process (often the requester, but not always the requester) to recover some memory (aka "OOM killer").
So your sudden deaths could have more to do with low RAM than with stray pointers. Running Gimp in a console and looking for the messages when it dies could provide some info (as would looking at system logs).
Edit: Something that escaped me: you are running 32-bit Gimp... So you are normally limited to 4GB RAM in the process (but then why 32-bit Gimp?)