[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

3300.0. "windows disappear" by CVG::ESONIS (What now?) Tue Sep 04 1990 14:29

    Hopefully someone can help with a minor problem I'm having... 
    I've been using an MV3500 running V5.3-2 decwindows. 
    Things work fine most of the time, but every so often all of 
    my decterms will just disappear. Most often it seems to happen 
    when I'm resizing a window, whether I use a "set term/wid=" 
    command, or use the customize menu. I have never been able to 
    find any trace of a process dump or information in any of the 
    decw*.log files which would point to a possible cause. 
    	Autogen/feedback has been run several times, without having
    any effect.
    
    - is there a way to trace a failure of this sort?
    
    - perhaps some applicable sysgen parameters aren't being 
    	set properly by the autogen?
    
    - Is this sort of bahaviour a known problem?
    
    Thanks for any help someone can offer....
    
    Steve e. ( obviously not an expert)
    
    
T.RTitleUserPersonal
Name
DateLines
3300.1HANNAH::MESSENGERBob MessengerTue Sep 04 1990 15:208
DECterm is probably running out of memory.  You can check this by looking
at the DECterm log file: define the logical name DECW$DECTERM_OUTPUT in
your LOGIN.COM to be the name of the log file that you want.

To give DECterm more memory, increase your PQL_DPGFLQUOTA parameter in
SYSGEN.

				-- Bob
3300.2io error 65535CVG::ESONISWhat now?Wed Sep 05 1990 10:3018
    Thanks for the help.... I defined the logical, and re-started my
    session. Shortly afterwards, the windows disappeared... the following 
    output log was produced:
    
    

DECterm version V2.0 now at your service...

To create DECterms, use the Session Manager or call the
DECwTermPort() routine from another process.
XIO:  fatal IO error 65535  on X server "ANSON::0.0"
      after 562 requests (562 known processed) with 0 events remaining.
    
    
    
    Is this what I should see if more memory is needed?  I'll probably add
    an increase for PQL_mumble anyways, and autogen again.....
    
3300.3HANNAH::MESSENGERBob MessengerWed Sep 05 1990 17:396
Re: .2

From the log file it looks like Xlib or the server might have dropped the
connection.  Is there anything "interesting" in the server log file?

				-- Bob
3300.4CVG::ESONISWhat now?Mon Sep 10 1990 09:2312
    
    
>From the log file it looks like Xlib or the server might have dropped the
>connection.  Is there anything "interesting" in the server log file?
    
    
    Unfortunately, the disk was purged before I could look.... Next time
    this happens, I'll check it out.
    
    Thx,
    
    /Steve e.
3300.5too many events?CVG::ESONISWhat now?Thu Nov 01 1990 06:3825
    
    Still haven't gotten anything from the server log, but the last time I
    lost my screens the decw$terminal_output.log contained the following:
    
    
DECterm version V2.0 now at your service...

To create DECterms, use the Session Manager or call the
DECwTermPort() routine from another process.
Warning: too many graphics expose events
Warning: too many graphics expose events
Warning: too many graphics expose events
Warning: too many graphics expose events
Warning: too many graphics expose events
Warning: too many graphics expose events
X Toolkit Error: Cannot perform calloc
    
    
    There were large numbers of the warning messages regarding "too many
    graphics expose events".... Do these mean that I'm using too many
    windows? If so, is there an adjustment to be made?  
    
    
    
3300.6DECWIN::MESSENGERBob MessengerThu Nov 01 1990 11:3911
Re :.5

"Warning: too many graphics expose events" is an internal error message which
indicates that there is a problem in DECterm's code that handles occluded
scrolling.  I should probably have removed this message from the shipped
version of DECterm since it is likely to confuse people.

Your problem is that the DECterm controller is running out of memory.  You
should increase your PQL_DPGFLQUOTA parameter in SYSGEN.

				-- Bob