Dear Gimpers
Thanks for the reply --- We have decided to upgrade to the new stable
version of gimp, 1.2.1 we already have it running on our new linux server
There are no comments, on the way I start my Perl-Gimp script. I had sent
the script which I use to call my charting programs.
Two major
On Wed, Jun 06, 2001 at 02:51:24PM +0200, Raphael Quinet <[EMAIL PROTECTED]> wrote:
> > write(1, "/usr/lib/gimp/1.1/plug-ins/Perl-Server (pid:308): [E]xit, [H]alt,
> show [S]tack trace or [P]roceed: ", 99) = 99
> > read(0, "", 4096) = 0
>
> This shows that you are affecte
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(
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 then,
On Tue, Jun 05, 2001 at 01:01:51PM +0530, Chetan Dhavse <[EMAIL PROTECTED]> wrote:
> It happened again --- and here is the trace (strace) during the time when
hmm, this doesn't look like a bug in gimp (not directly, that is).
> (2 sec. generated > 15000 such lines) and Perl-Server shows 99% of C
Hi!!
This is Chetan again I did follow the discussion on the stability issue
of gimp. but back to the main question.
It happened again --- and here is the trace (strace) during the time when
the process hanged and I have not been able to pin-point as to where the
problem lies. You see I use gim
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
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
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 m
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 cycli
On Fri, Jun 01, 2001 at 08:16:13PM +0200, Raphael Quinet <[EMAIL PROTECTED]> wrote:
> Hey, this looks like a serious problem!
>
> recommend to use an old version such as 1.1.4, then they
> should definitely be fixed in 1.2.2, otherwise it is
> ridiculous to call this a "stable release"...
It's s
On 1 Jun, Raphael Quinet wrote:
> Now I see for the first time a comment saying that some old
> unstable release is more stable than 1.2.x, so I am a bit
> surprised... I would like you to elaborate a bit on the
> stability problems of 1.2.x, and if possible to report this
> in bugzilla.
> If
On Sat, 26 May 2001, Marc Lehmann wrote:
> 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 successio
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 m
14 matches
Mail list logo
