Re: Suggestion for the VMS X-windows server
- From: JF Mezei <jfmezei.spamnot@xxxxxxxxxxxxx>
- Date: Sun, 18 Mar 2007 16:35:14 -0400
FredK wrote:
It isn't clear to me that it has "run out of resources". Becomming unresponsive doesn't meet the criteria. If the X server "runs out of memory" --- it crashes (or sometimes if you are lucky it kills a connection) - it doesn't just "slow down".
With Mozilla, I see the X server's process raise its Working set to wsextent, and raise its virtual pages to very near pgfilquota. Show proc/quota reveals it has 256 pages left as pgfilquota.
At this point in time, mozilla does not redraw the window. Menus do not appear, however, looking at the mozilla process (show proc/cont), I see some tiny action when the mouse moves over a clickable area such as the menu mar that should be just under the MWM window title. (MWM works fine during those situations, it is just the content of all mozilla windows that do not refresh).
Bringing other simpler windows to the foreground (such as decterm), they work perfectly, and they redraw fine.
There are errors logged to decw$server_0_error.log about insufficient resources (but I currently have no examples since I have not gone to any complex/large web pages since restarting the x server).
.
- Follow-Ups:
- Re: Suggestion for the VMS X-windows server
- From: FredK
- Re: Suggestion for the VMS X-windows server
- References:
- Suggestion for the VMS X-windows server
- From: JF Mezei
- Re: Suggestion for the VMS X-windows server
- From: FredK
- Re: Suggestion for the VMS X-windows server
- From: Michael Kraemer
- Re: Suggestion for the VMS X-windows server
- From: FredK
- Suggestion for the VMS X-windows server
- Prev by Date: Re: AMD's well may be running dry
- Next by Date: Re: AMD's well may be running dry
- Previous by thread: Re: Suggestion for the VMS X-windows server
- Next by thread: Re: Suggestion for the VMS X-windows server
- Index(es):
Relevant Pages
|