Xref: utzoo gnu.emacs:1549 gnu.emacs.bug:1126 comp.windows.x:13179 Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!bbn!ulowell!m2c!bergman From: bergman@m2c.m2c.org (Michael Bergman) Newsgroups: gnu.emacs,gnu.emacs.bug,comp.windows.x Subject: gnu-emacs 18.54 problem under X11 on Vax 8530 Message-ID: Date: 7 Sep 89 20:19:01 GMT Sender: news@m2c.ORG Distribution: gnu Organization: Massachusetts Microelectronics Center, Westborough, MA Lines: 41 We recently upgraded from Ultrix 2.2 running X10 to Ultrix 3.0 running X11, and simultaneously went from gnuemacs 18.51 to 18.54, and I took over maintaining emacs at our site. We are having a problem with emacs freezing up. There are two error messages I am getting: on startup: X Toolkit Warning: Cannot allocate colormap entry for "#0000000000 " (the satartup error message hits for several other applications as well) and once frozen: Xlib: sequence lost (0x10000 > 0xf9ca) in reply type 0x0! Xlib: sequence lost (0x20000 > 0x109be in reply type 0x0! Xlib: sequence lost (0x20000 > 0x109c3 in reply type 0x0! Xlib: sequence lost (0x20000 > 0x10de6 in reply type 0x0! Xlib: sequence lost (0x20093 > 0x111b3 in reply type 0x12! or something similar. While emacs is frozen, it eats up large quantities of resources, on the order of 50% of the cpu, causing a serious slowdown for everyone on the system, and, of course, my own other windows (for a while I thought it was a problem at the server end, until someone came over to complain about "whatever I was doing with emacs"). We are running emacs on a VAX 8530, and my server is a VAXStation 2000. Another user is experiencing the same problems running emacs (same image) on a GPX locally. There are no problems when running emacs in the "-nw" mode. Has anyone else out there experienced this behaviour? Is there an easy fix? Your help is appreciated. -- --mike bergman Massachusetts Microelectronics Center 75 North Drive, Westborough, MA 01581, USA +1 (508) 870-0312 UUCP: harvard!m2c!bergman INTERNET: bergman@m2c.org