bug#27816: 26.0.50; X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55

[martin rudalics <rudalics@gmx.at>]

[-- Attachment #1: Type: text/plain, Size: 2283 bytes --]

I can give the following additional information on this:


With a Lucid build from 23.8.2014 I get an incompletely drawn frame
(screenshot attached).  Clearly, drawing the scroll bar has not finished
yet.  A screenshot of a complete frame is attached for comparison.  In
the terminal Emacs the message

get-device-terminal: Display :0.0 does not exist

is displayed.


With a build from 9.11.2014 I get the same behavior but with the
meanwhile well-known message:

X protocol error: BadPixmap (invalid Pixmap parameter) on protocol request 55

In addition, the Emacs process consumes all CPU power it can get.


With current master the client frame is shown for a short moment and
then disappears.  The Emacs process does not stall.


In all cases, the problem occurs reliably - on the average about every
fifth call of emacsclient.  Lucid without toolkit scrollbars doesn't
build here any more, so far no idea why [does anyone grok ...

In file included from ./string.h:49:0,
                  from ../../lib/explicit_bzero.c:28:
./stddef.h:93:3: error: conflicting types for ‘max_align_t’
In file included from ./stddef.h:55:0,
                  from ./string.h:49,
                  from ../../lib/explicit_bzero.c:28:
/usr/lib/gcc/x86_64-linux-gnu/4.7/include/stddef.h:426:3: note: previous declaration of ‘max_align_t’ was here
make[1]: *** [explicit_bzero.o] Fehler 1
make[1]: *** Warte auf noch nicht beendete Prozesse...
In file included from ./unistd.h:56:0,
                  from ../../lib/fcntl.c:28:
./stddef.h:93:3: error: conflicting types for ‘max_align_t’
In file included from ./stddef.h:55:0,
                  from ./unistd.h:56,
                  from ../../lib/fcntl.c:28:
/usr/lib/gcc/x86_64-linux-gnu/4.7/include/stddef.h:426:3: note: previous declaration of ‘max_align_t’ was here

... I haven't built this for years?].  A motif build of master doesn't
exhibit this behavior but gets the Emacs process aborted here around
every seventh invocation of the client.  A gtk build exhibits no
problems AFAICT and a build without X toolkit support works well too.

BTW, I never use emacsclient and have no idea how to use it.  Is there a
way to stop the server from the starting emacs?

martin

[-- Attachment #2: incomplete frame - 2017-08-03.png --]
[-- Type: image/png, Size: 17148 bytes --]

[-- Attachment #3: complete frame - 2017-08-03.png --]
[-- Type: image/png, Size: 36537 bytes --]