On Tuesday 08 April 2003 15:56, Ruslan Ermilov wrote: > On Tue, Apr 08, 2003 at 03:53:52PM +0200, CARTER Anthony wrote: > > Is the problem during xclock execution or xclock compilation? > > At runtime. When I run xclock under truss(1), it shows the > paths to the fonts, and never stops doing it, eventually > eating all memory and being killed by kernel. I remember someone telling about those exact symptoms on IRC... after the last updates to Xft _before_ the updates you suspect of causing trouble. He eventually got rid of it by some furious recompiling of XFree & friends, but we never got a fix on what really broke. FWIW ... -- Regards, Michael Nottebrock
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:03 UTC