I can't answer the question but this prompts a related question. If you
processing in a shared hosting situation, how do you tell that your
scripts are chewing up memory, or are you being informed by your
provider that this is happening? -Bob
Mike wrote:
I'm switching servers and something is apparently wrong with the setup
on the new server. Perl scripts that use Image::Magick worked fine on
the other server, but don't work on this one and use up the server
memory and a huge chunk of the CPU until I kill the process. I did
some searching and found
http://studio.imagemagick.org/pipermail/magick-users/2003-January/007069.html
and it said:
After a crash, do:
convert --version
gdb `which perl` core
bt
Here is what I got from that:
[EMAIL PROTECTED] Counters]# convert --version
Version: ImageMagick 6.3.5 08/05/07 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2007 ImageMagick Studio LLC
[EMAIL PROTECTED] Counters]# gdb `which perl` core
GNU gdb Red Hat Linux (6.3.0.0-1.143.el4rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "i386-redhat-linux-gnu"...(no debugging
symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
/var/cpanel/Counters/core: No such file or directory.
(gdb)
(gdb) bt
No stack.
(gdb) q
Anyone know what the problem is and how to fix it?
Mike
_______________________________________________
Magick-users mailing list
[email protected]
http://studio.imagemagick.org/mailman/listinfo/magick-users
