On Tue, Jun 05, 2001 at 01:01:51PM +0530, Chetan Dhavse <cdhavse@xxxxxxxx> 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 CPU
> used in the 'top'
>
> write(1, "/usr/lib/gimp/1.1/plug-ins/Perl-"..., 101) = 101
> read(0, "", 4096) = 0
this looks as if the perl-server outputs an error message and then tries
to read from stdin, which is... probably connected to /dev/null or so. How
do you start gimp & the server? could you start in interactively (e.g.
inside a screen?) or re-run the strace with the "-s9999" switch, so we can
see the full error message (strace clips strings).
It's especially mysterious why it is trying to _read_ from stdin, my guess
is that this is (yet again) the endless-loop-in-libgimp bug.
You can test the latter by starting gimp with "--enable-stack-trace never".
if the perl-server then dies immediately instead of sucking cpu time then
this is the problem you hit.
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@xxxxxxxx |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
