Here's how to avoid some X-related crashes in gvim (with GTK2), Firefox, et al.
- There are known bugs in the GTK2 and/or Xorg software which "may" cause
crashes (with a message of several lines on syserr) in programs using
them. I've had such crashes (so far) in Firefox (which, on Linux, is
compiled with a GTK2 GUI at Mozilla) and in gvim (which I compile with
The workaround is quite simple: add the --sync switch to the
command-line (console-mode Vim doesn't need it, even if GUI-enabled and
even when using the X cliboard, because it creates no new X-windows).
This is of course just a "workaround", not a "fix". The Gnome and/or
Xorg developers are looking for a fix, which (when found and tested)
hopefully someday Linux distributors will make available to their users.
The downside of this workaround is a slowdown which may be quite
noticeable when e.g. retracing a maximized gvim using a small 'guifont'
(I regard this slowdown as not as bad as a startup crash but YMMV ;-) ).
See for instance https://bugzilla.gnome.org/show_bug.cgi?id=581526#c0
describing how the "misunderstanding" (leading to a crash) between GTK2
and X might occur.
See also http://bugs.freedesktop.org/show_bug.cgi?id=20254 for one X11
bug which has been recently fixed, but not yet ported to every Linux
distribution (for instance, on openSUSE which I use, the so-called
"Factory" build has been fixed 11 days ago, but I can still expect some
"waiting time" until that fix is deemed to have baked long enough on
Factory to be ported to Release).
P.S. Not sure if this message is "untechnical" enough for the vim_use list.
Really heard in court in the U.S.A.:
Q.: That myasthenia gravis, does it affect your memory?
A.: Yes, it does.
Q.: In what way does it affect your memory?
A.: I forget.
Q.: Could you give us an example of something that you've forgotten?
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php