Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!clyde.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!samsung!dali.cs.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!magnus.ircc.ohio-state.edu!csn!datran2!smb From: smb@csn.org!datran2 Newsgroups: comp.sys.next Subject: Re: 2.0 bug (or feature?) Message-ID: <1991Feb19.183438.16518@csn.org!datran2> Date: 19 Feb 91 18:34:38 GMT References: <432G31*o@cs.psu.edu> <6988@emory.mathcs.emory.edu> Organization: Data Transforms, Inc. Lines: 23 In article gessel@ilium.cs.swarthmore.edu (Daniel Mark Gessel) writes: >This is the window server dying and restarting, I'm pretty sure. I've >had similar problems when sending rude postscript through YAP. I'm >trying to remember exactly what I was doing. I think it was in a for >loop, and I ended up scaling by 1.0/loopvariable, and the loopvariable >went through 0. I think that killed the window server (and I can see >why, it'd take a while to draw anything with that scaling). I had the same reaction when I tried to display postscript that had an object scaled to 0. This took a while to track down, because the window server didn't die until I quit Preview. Also this is old data from 1.0. I don't know if the same is true of 2.0. It seems to me that an application such as Preview or Yap should not be able to kill the window server. Perhaps this is a practical impossibility, but is an ideal to strive for. Steve. -- #====#====#====#====#====#====#====#====#====#====#====#====#====#====#====# # Steve Boker # "Badgers, we don't have no stinking badgers" # # smb@data.com # -from Treasure of the Sierra Madre Zoo # #====#====#====#====#====#====#====#====#====#====#====#====#====#====#====#