rmilner@zia.aoc.nrao.edu (Ruth Milner) (03/05/91)
The non-programmers here have recently started to use OpenWindows, and
have naturally uncovered a few problems.
First, one user is running on a Sun 3/80 and has encountered absolutely
miserable performance on it. He has about 40MB local swap, 8MB memory, no
load on the machine (and not a lot of windows running), etc. Generally it takes
several seconds after he moves the mouse for the cursor to actually move and
the focus to follow it. We have other people using 3/60's with less swap who
have not observed this problem. He says he talked to a colleague elsewhere
with a 3/80 who has also seen this sort of behaviour. Is this borne out by
other people's experience? Is there something I can do, or is it just generic
to 3/80's? For the record, Sunview performs vastly better on this system than
OpenWindows.
Second, another person has noticed that if he goes away (sometimes leaving
long jobs running in the background, sometimes not) and leaves the console
idle for around 24 hours or longer, when he comes back and resumes work, the
windows appear in black-and-white instead of colour, menus do not activate
properly, etc., and he has to restart OpenWindows to get it back to normal.
"screenblank" is running on the system (an SS1), but it activates after 10
minutes idle time on the console, and this weirdness does not kick in until
many hours later than that. Is the problem with screenblank, OpenWindows,
or somehow with their interaction? Has anyone else seen or heard of this?
Please note that I am posting from a different machine than the return address;
my regular news system does not seem to carry this group.
Thank you very much.
--
Ruth Milner
Systems Manager NRAO/VLA Socorro NM
rmilner@zia.aoc.nrao.edudgh@Unify.com (David Harrington) (03/07/91)
In article <1991Mar4.223608.6090@helios.physics.utoronto.ca>, rmilner@zia.aoc.nrao.edu (Ruth Milner) writes: > > Second, another person has noticed that if he goes away (sometimes leaving > long jobs running in the background, sometimes not) and leaves the console > idle for around 24 hours or longer, when he comes back and resumes work, the > windows appear in black-and-white instead of colour, menus do not activate > properly, etc., and he has to restart OpenWindows to get it back to normal. > "screenblank" is running on the system (an SS1), but it activates after 10 > minutes idle time on the console, and this weirdness does not kick in until > many hours later than that. Is the problem with screenblank, OpenWindows, > or somehow with their interaction? Has anyone else seen or heard of this? > I had a bunch of wierdness like this that I couldn't explain, either. Looking over the OW bug list, I noticed that there was a reported memory leak in the xview analog clock. I checked it out, and BOY is there! So I started using dclock, and everything is fine. -- David Harrington internet: dgh@eire.unify.COM Unify Corporation ...!{csusac,pyramid}!unify!eire!dgh 3901 Lennane Drive voice: +1 916 928-6255 Sacramento, CA 95834 fax: +1 916 928-6401