Mercurial > emacs

comparison etc/PROBLEMS @ 100504:362e5c86fb72

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Add Gtk+ version to last change.
author Jan Djärv <jan.h.d@swipnet.se>
date Thu, 18 Dec 2008 19:19:00 +0000
parents 27f8c0a5cb19
children c49d80bdf651
comparison
equal deleted inserted replaced
100503:27f8c0a5cb19 100504:362e5c86fb72
237 237
238 This is related to the bug above. A scenario for this is when emacs is run 238 This is related to the bug above. A scenario for this is when emacs is run
239 as a server, and an X frame is created. If the X server for the frame 239 as a server, and an X frame is created. If the X server for the frame
240 crashes or exits unexpectedly and an attempt is made to create a new 240 crashes or exits unexpectedly and an attempt is made to create a new
241 frame on another X display, then a Gtk+ error happens in the emacs 241 frame on another X display, then a Gtk+ error happens in the emacs
242 server that results in an endless loop. 242 server that results in an endless loop. This is not fixed in any known
243 Gtk+ version (2.14.4 being current).
243 244
244 ** Emacs compiled with Gtk+ crashes on startup on Cygwin. 245 ** Emacs compiled with Gtk+ crashes on startup on Cygwin.
245 246
246 A typical error message is 247 A typical error message is
247 ***MEMORY-ERROR***: emacs[5172]: GSlice: failed to allocate 504 bytes 248 ***MEMORY-ERROR***: emacs[5172]: GSlice: failed to allocate 504 bytes