[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:	DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:	See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:	STAR::VATNE

Created:	Mon Oct 30 1989
Last Modified:	Mon Dec 31 1990
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3726
Total number of notes:	19516

2752.0. "Cannot Customize the Window...HELP" by ASD::RAMAN () Fri May 11 1990 17:05

	I am running DecWindows under VMS 5.4 on my GPX. Whenever I try to
	customise the Decterm window (by picking Window option) all the windows
	and applications blow away. This doesn't happen if I select some other
	option (e.g. Display) for customization.

	The Decw$server_0_error.log gives the following log
		"Connection 27a670 is closed by Txport".

	Does anyone know what is happening here and what is the fix ?

	thanks,
	-/rajesh

T.R Title User Personal
Name Date Lines

2752.1 DECterm controller out of resource STAR::ORGOVAN Vince Orgovan Mon May 14 1990 18:13 14

T.R	Title	User	Personal Name	Date	Lines
2752.1	DECterm controller out of resource	STAR::ORGOVAN	Vince Orgovan	`Mon May 14 1990 18:13`	14
	Usually all DECterm windows on a workstation are handled by a single multithreaded DECterm controller. If the DECterm controller crashes, it takes down all your DECterm windows with it. There are a couple of errors that the controller doesn't gracefully handled, including calling lib$get_vm to allocate the memory it needs at runtime. It is possible that the memory needed to display the Customize/Window dialog box is enough to push the controller over the threshold. If this is the problem, you should be able to verify it by doing a "show proc /continuous" display on the DECterm controller process (i.e. DECW$TE_n). Look at the virtual pages count. If it's dangerously close to the SYSGEN parameter VIRTUALPAGECNT then this is likely to be the problem.

    Usually all DECterm windows on a workstation are handled by a 
    single multithreaded DECterm controller. If the DECterm controller
    crashes, it takes down all your DECterm windows with it. There are
    a couple of errors that the controller doesn't gracefully handled,
    including calling lib$get_vm to allocate the memory it needs at
    runtime. It is possible that the memory needed to display the
    Customize/Window dialog box is enough to push the controller over
    the threshold. 
    
    If this is the problem, you should be able to verify it by doing
    a "show proc /continuous" display on the DECterm controller 
    process (i.e. DECW$TE_n). Look at the virtual pages count. If it's
    dangerously close to the SYSGEN parameter VIRTUALPAGECNT then this
    is likely to be the problem.