Zharf tried to fight back!

David Taylor (n9506769@garbo.nepean.uws.edu.au)
Sun, 23 Aug 1998 17:41:29 +1000


I reported a bug to the list a while ago whereby Netscape would gobble
up all the CPU time *after* it had been killed.  Well, today I started
up Zharf in order to have a look and a fiddle. I quickly concluded that
it was the ugliest thing I'd ever seen and then decided to be done with
it.  I killed Zharf using it's own "Kill" button.  Well, straight after
that my CPU usage shot thru the roof!  Below is a capture from top,
taken shortly after killing Zharf.

  PID USER     PRI  NI  SIZE  RSS SHARE STAT  LIB %CPU %MEM   TIME
COMMAND
10460 dtaylor   12   0   796  796   652 R       0 95.5  0.8  25:47 Zharf

This shows that Zharf's still alive and kicking... and hungry!

The reason I bring this up is that in response to my query about
netscape I was told that it was the fault of netscape communicator. 
Well, now it has happened with Zharf.  Do these programs just *happen*
to exhibit the same problems under the same conditions?  Or, is it
deviously linked back to AfterStep somehow?  Or, is it possibly just
something specific to my system?

BTW, I run RedHat 5.0 and AfterStep 1.4.5.55N6.

-- 
Regards,
David Taylor

+============================================+
| University of Western Sydney - Nepean      |
| dtaylor@cit.nepean.uws.edu.au              |
| http://www.cit.nepean.uws.edu.au/~dtaylor/ |
+============================================+


--
   WWW:   http://www.afterstep.org/
   FTP:   ftp://ftp.afterstep.org/
   MAIL:  http://www.caldera.com/linuxcenter/forums/afterstep.html