Ghostscript gave up the ghost
I have an odd problem with ghostscript on my work machine.
Both home machine and work machine run kernal 2.2.3 and debian 2.1
Work machine has 48M RAM, home machine 32M. Both has 64M swap.
Ghostscript work fine on my home machine, producing nice output on my
deskjet 310.
Ghostscript used to work fine on the work machine too, producing
even better output on a laserjet III connected via a novell server
on a token ring. But it went wrong suddenly. Printing any ps file
at work will start gs as expected, but gs just eat memory and use
99% of the cpu for a long time, according to "top". Memory usage increase
steadily until 80% or so, then the trashing begins. gs still eat
memory but only use 2% cpu due to excessive paging and the machine is
very unresponsive, until "lprm" saves the day.
This happen even with simple .ps-files that worked before, and still
print quickly on the smaller home machine. I don't think gs has
been replaced in the meantime, although I did upgrade from
a late "frozen" slink to "released" slink when this happened.
But X was the only stuff upgraded, everything else was upgraded
already. And the same gs binary works at home.
There is nothing wrong with the networking or
magicfilter setup, ascii files prints just fine.
Do anybody have any idea about what might be wrong? Or at least
a suggestion to get this working?
I can no longer use lyx at work :-(
Helge Hafting
Reply to: