On Sat, Sep 21, 2013 at 02:20:52AM +0100, Ken Moffat wrote: > > I'll leave it for a bit longer (somehow I never seem to keep > regular hours these days!), but I'll probably kill it in the end. > What is really odd is that bison isn't actually using memory, as if > it is in a code loop. 'top' showed the following a few minutes ago: > > top - 02:10:50 up 12:38, 1 user, load average: 1.08, 1.51, 1.59 > Tasks: 108 total, 2 running, 106 sleeping, 0 stopped, 0 zombie > Cpu(s): 12.3%us, 87.4%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.3%hi, 0.0%si, 0.0%st > Mem: 1999912k total, 1966028k used, 33884k free, 261528k buffers > Swap: 2929684k total, 320k used, 2929364k free, 1299576k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 5382 root 20 0 2316 816 696 R 97.7 0.0 78:51.06 bison > > and now (8 min later) bison's memory usage hasn't changed although > it has been running at 95%+ of CPU for all the extra time. > Killed it after more than 200 minutes CPU - memory use hadn't changed, it was still using as much CPU as it could get, nothing more in the output.
ĸen -- das eine Mal als Tragödie, dieses Mal als Farce
