bug#17237: 24.3.50; Hang with X11 + emacsclient

bug#17237: 24.3.50; Hang with X11 + emacsclient

[Aaron Ecay]

I observe strange hangs when using org-protocol via emacsclient, under
X11.  Recipe to reproduce:

1. emacs -Q (recent trunk version; I’ve been seeing the bug for several
   weeks if not longer)
2. M-x server-start
3. touch ~/test

If I invoke the following command from a shell on the same X11 virtual
desktop as emacs, it works fine:

emacsclient ~/test

However, if I invoke the same command from a terminal on another
desktop, the CPU usage spikes of both emacs (to ~50%) and the X server
process (to ~85%), as visible in top.  emacsclient prints "Waiting for
Emacs..." to the terminal, and does not exit.

The processes will stay in this busy hang until I switch to the virtual
desktop with the emacs frame on it, at which point the file will open in
emacs.  (I suspect that the file does not open earlier, as sometimes I
can see a brief glimpse of the previous buffer when switching to emacs’s
desktop, before the buffer called for by emacsclient replaces it.)

I can then edit normally and exit the server buffer normally with C-x #
causing the emacsclient to exit in the terminal window.

Possibly relevant software versions:
- Arch Linux
- X.org server version 1.15.0-5
- Window manager = a devel version of xmonad (most recent commit is:
  Sat Jul 20 15:21:24 EDT 2013  Adam Vogt <vogt.adam@gmail.com>)

Thanks,
Aaron



In GNU Emacs 24.3.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 3.10.7)
 of 2014-04-06 on haize
Windowing system distributor `The X.Org Foundation', version 11.0.11500000
Configured using:
 `configure --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib
 --localstatedir=/var --mandir=/usr/share/man
 --enable-link-time-optimization --with-sound=alsa --without-gconf
 --with-x-toolkit=gtk3 --with-xft 'CFLAGS=-march=x86-64 -mtune=generic
 -O2 -pipe -fstack-protector --param=ssp-buffer-size=4'
 CPPFLAGS=-D_FORTIFY_SOURCE=2
 LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro'

Important settings:
  value of $LC_COLLATE: C
  value of $LANG: en_US.UTF-8
  locale-coding-system: utf-8-unix

Major mode: Org

Minor modes in effect:
  TeX-source-correlate-mode: t
  rcirc-track-minor-mode: t
  auto-insert-mode: t
  flyspell-mode: t
  erefactor-check-eval-mode: t
  magit-auto-revert-mode: t
  diff-auto-refine-mode: t
  auto-revert-mode: t
  desktop-save-mode: t
  electric-pair-mode: t
  typopunct-mode: t
  which-function-mode: t
  global-goto-address-mode: t
  goto-address-mode: t
  shell-dirtrack-mode: t
  global-undo-tree-mode: t
  undo-tree-mode: t
  show-paren-mode: t
  yas-global-mode: t
  yas-minor-mode: t
  sml-modeline-mode: t
  ido-everywhere: t
  minibuffer-depth-indicate-mode: t
  icomplete-mode: t
  command-frequency-autosave-mode: t
  command-frequency-mode: t
  savehist-mode: t
  recentf-mode: t
  global-auto-complete-mode: t
  auto-complete-mode: t
  tooltip-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  column-number-mode: t
  line-number-mode: t
  auto-fill-function: org-auto-fill-function
  transient-mark-mode: t
  abbrev-mode: t

Recent input:
M-x r e p o r t <tab> <return>


-- 
Aaron Ecay

bug#17237: 24.3.50; Hang with X11 + emacsclient

[Jan Djärv]

Hello.

2014-04-11 02:48, Aaron Ecay skrev:
>
> I observe strange hangs when using org-protocol via emacsclient, under
> X11.  Recipe to reproduce:
>
> 1. emacs -Q (recent trunk version; I’ve been seeing the bug for several
>     weeks if not longer)
> 2. M-x server-start
> 3. touch ~/test
>
> If I invoke the following command from a shell on the same X11 virtual
> desktop as emacs, it works fine:
>
> emacsclient ~/test
>
> However, if I invoke the same command from a terminal on another
> desktop, the CPU usage spikes of both emacs (to ~50%) and the X server
> process (to ~85%), as visible in top.  emacsclient prints "Waiting for
> Emacs..." to the terminal, and does not exit.

XMonad does not make the Emacs frame visible, so Emacs gets stuck in an 
endless loop.  Many other wm:s change the desktop to the desktop where Emacs 
is, but XMonad does not.
Possible we could force that with some EWMH-hints, but the XMonad 
documentation suggests that a user may configure XMonad to ignore those anyway.

Se the best we can do is to prevent the endless loop.  I have checked in a fix 
in the emacs-24 branch.

	Jan D.

bug#17237: 24.3.50; Hang with X11 + emacsclient

[Aaron Ecay]

Hi Jan,

2014ko apirilak 17an, Jan Djärv-ek idatzi zuen:
>
>
> XMonad does not make the Emacs frame visible, so Emacs gets stuck in an
> endless loop.  Many other wm:s change the desktop to the desktop where Emacs
> is, but XMonad does not.
> Possible we could force that with some EWMH-hints, but the XMonad
> documentation suggests that a user may configure XMonad to ignore those anyway.
>
> Se the best we can do is to prevent the endless loop.  I have checked in a fix
> in the emacs-24 branch.

I’ve built the code with your fix and can confirm I no longer see the
bug.

Thanks,

--
Aaron Ecay