Dear Gimpers
Thanks for such a prompt reply --- when one is lost like the way I am
There is this wonderful mailing list
[What would I have done without internet :-(]
I had posted a question about -- which is the best way to start
gimp. [this was some time back].
I had received no reply
On Wed, 06 Jun 2001, Chetan Dhavse wrote:
[...]
[--enable-stack-trace {never|query|always} option is not available in
with gimp 1.1.04]
[...]
This is the strace -p -s o/p
#
read(0, , 4096) = 0
getpid()
On 2 Jun, Sven Neumann wrote:
I'd like to see your script or at least have a description of what it
did so we can try to debug the behaviour you are describing. Using
memprof it should be possible to find your leaks.
The last time I checked GIMP with memprof it didn't show any unexpected
Hi,
Marc Lehmann [EMAIL PROTECTED] writes:
It's simple: i had(!) a script which loaded and analyzed thousands of
(checked) jpegs and (unchecked) gifs. Broken gifs tend to hurt gimp badly,
with effects ranging from gimp filling all virtual memory to segfaulting
(and yes, sometimes cycling in
On 2 Jun 2001, Sven Neumann wrote:
Hi,
Marc Lehmann [EMAIL PROTECTED] writes:
It's simple: i had(!) a script which loaded and analyzed thousands of
(checked) jpegs and (unchecked) gifs. Broken gifs tend to hurt gimp badly,
with effects ranging from gimp filling all virtual memory to
On Sat, Jun 02, 2001 at 12:54:23AM +0200, Sven Neumann [EMAIL PROTECTED] wrote:
you are aware that there's a command-line option to control the stack-trace
behaviour?
yes.
I'd like to see your script or at least have a description of what it did
the inner loop was this (i cannot run it at
On Thu, May 24, 2001 at 02:11:54PM +0530, Chetan Dhavse [EMAIL PROTECTED] wrote:
I am using Gimp 1.1.4(I find this version more stable)
same here.. gimp-1.2 has big stability and memory problems when it
encounters lots of images in succession.
The problem is the programs just hangs after
