| 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 |
A customer of ours has reported the following problem. Sometime during the execution of their application code it appears that the DECwindows window manager has terminated. We are still trying to get more information as to what led up to this. In the file DECW$WINMGR_OUTPUT the following is found: Fatal XIO error DECW-E-CNXABORT, connection aborted DPY:1437688 Is there anyone out there that would like to take a stab at a possible cause/reason that this happened ? I realize there's not a lot of info to go on at this time, but any insight would be appreciated. Thanx, -=> Jim <=-
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3313.1 | more info...sorry | GSRC::WEST | SCARY : A programmer with a screwdriver. | Thu Sep 06 1990 17:52 | 11 |
Oh yea...by the way... VS 3520 8 Plane 48M VAX VMS V5.3-1 DECwindows V2.0 (XUI) -=> Jim <=- | |||||
| 3313.2 | Unsolved problem | STAR::VATNE | Peter Vatne, VMS Development | Tue Oct 02 1990 11:24 | 13 |
Thanks for supplying the version information. Well, unfortunately, this looks like one of those many unsolved problems we have on our desk. The window manager should be using the local transport, which should never abort the connection like this. All we can do right now is collect more information, and try to think how things could get to this state. We will probably have to add more debugging code in the next version of DECwindows to catch this problem. Can you tell us how often the customer gets sees this problem? Was the screen particularly busy at the time, not just drawing, but popping windows up, or moving them, or iconifying them? | |||||