unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#45737: 27.1.50; Assertion failure in window_box_height
@ 2021-01-09  9:33 martin rudalics
  2021-01-09 10:00 ` Eli Zaretskii
  2022-02-07  1:05 ` Lars Ingebrigtsen
  0 siblings, 2 replies; 12+ messages in thread
From: martin rudalics @ 2021-01-09  9:33 UTC (permalink / raw)
  To: 45737

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

With the current release version running emacs -Q, evaluating

(progn
   (tab-line-mode)
   (split-window (split-window) nil t)
   (split-window)
   (split-window (split-window nil nil t) nil t))

and resizing the frame by dragging its lower right corner with the mouse
to very small rectangles I can trigger the following assertion failure:

../../src/xdisp.c:1170: Emacs fatal error: assertion failed: height >= 0

The backtrace

(gdb) bt
#0  0x000000000063e1b3 in terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at ../../src/emacs.c:379
#1  0x000000000075894d in die (msg=0x96109c "height >= 0", file=0x961032 "../../src/xdisp.c", line=1170) at ../../src/alloc.c:7240
#2  0x0000000000458382 in window_box_height (w=0x149d100) at ../../src/xdisp.c:1170
#3  0x00000000004212da in required_matrix_height (w=0x149d100) at ../../src/dispnew.c:1740
#4  0x000000000042147d in allocate_matrices_for_window_redisplay (w=0x149d100) at ../../src/dispnew.c:1806
#5  0x00000000004220ed in adjust_frame_glyphs_for_window_redisplay (f=0x1422c60) at ../../src/dispnew.c:2123
#6  0x0000000000421547 in adjust_frame_glyphs (f=0x1422c60) at ../../src/dispnew.c:1827
#7  0x00000000004fd9f9 in resize_mini_window_apply (w=0x149d100, delta=-72) at ../../src/window.c:5216
#8  0x00000000004fdb98 in grow_mini_window (w=0x149d100, delta=18) at ../../src/window.c:5251
#9  0x0000000000481952 in resize_mini_window (w=0x149d100, exact_p=false) at ../../src/xdisp.c:11715
#10 0x0000000000480969 in display_echo_area_1 (a1=21614848, a2=XIL(0)) at ../../src/xdisp.c:11557
#11 0x000000000047fc66 in with_echo_area_buffer (w=0x149d100, which=1, fn=0x480933 <display_echo_area_1>, a1=21614848, a2=XIL(0)) at ../../src/xdisp.c:11327
#12 0x00000000004808de in display_echo_area (w=0x149d100) at ../../src/xdisp.c:11523
#13 0x0000000000483022 in echo_area_display (update_frame_p=false) at ../../src/xdisp.c:12038
#14 0x00000000004898c5 in redisplay_internal () at ../../src/xdisp.c:15456
#15 0x000000000048b5e3 in redisplay_preserve_echo_area (from_where=11) at ../../src/xdisp.c:16125
#16 0x000000000084ed6c in wait_reading_process_output (time_limit=30, nsecs=0, read_kbd=-1, do_display=true, wait_for_cell=XIL(0), wait_proc=0x0, just_wait_proc=0) at ../../src/process.c:5482
#17 0x000000000042cbb2 in sit_for (timeout=make_fixnum(30), reading=true, display_option=1) at ../../src/dispnew.c:6064
#18 0x000000000064fe21 in read_char (commandflag=1, map=XIL(0x10878b3), prev_event=XIL(0), used_mouse_menu=0x7fffffffe10f, end_time=0x0) at ../../src/keyboard.c:2738
#19 0x00000000006621ef in read_key_sequence (keybuf=0x7fffffffe2a0, prompt=XIL(0), dont_downcase_last=false, can_return_switch_frame=true, fix_current_buffer=true, prevent_redisplay=false) at ../../src/keyboard.c:9554
#20 0x000000000064b774 in command_loop_1 () at ../../src/keyboard.c:1350
#21 0x00000000007afe18 in internal_condition_case (bfun=0x64b2f8 <command_loop_1>, handlers=XIL(0x90), hfun=0x64a907 <cmd_error>) at ../../src/eval.c:1356
#22 0x000000000064aedd in command_loop_2 (ignore=XIL(0)) at ../../src/keyboard.c:1091
#23 0x00000000007af2cc in internal_catch (tag=XIL(0xd110), func=0x64aeb0 <command_loop_2>, arg=XIL(0)) at ../../src/eval.c:1117
#24 0x000000000064ae7b in command_loop () at ../../src/keyboard.c:1070
#25 0x000000000064a3ee in recursive_edit_1 () at ../../src/keyboard.c:714
#26 0x000000000064a5e6 in Frecursive_edit () at ../../src/keyboard.c:786
#27 0x00000000006409ef in main (argc=4, argv=0x7fffffffe798) at ../../src/emacs.c:2066

Lisp Backtrace:
"redisplay_internal (C function)" (0x0)
(gdb) frame 2
#2  0x0000000000458382 in window_box_height (w=0x149d100) at ../../src/xdisp.c:1170
1170	  eassert (height >= 0);
(gdb) p height
$2 = -54
(gdb)

indicates that the total height of one of the windows dropped to -54
pixels.  The problematic code is in 'window-sizable' which is not
prepared for the case that window sizes can drop below their minimum
size, something which can happen when a frame with many windows is made
very small.  I propose the attached patch to fix this.  OK to install?

martin


In GNU Emacs 27.1.90 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.5)
  of 2021-01-09 built on restno
Repository revision: 74d18957b898e687dcc07ba86559367c8d8ba482
Repository branch: emacs-27
Windowing system distributor 'The X.Org Foundation', version 11.0.12004000
System Description: Debian GNU/Linux 10 (buster)

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.

Configured using:
  'configure --with-gif=ifavailable --with-tiff=ifavailable
  --with-gnutls=no --without-pop --enable-gcc-warnings=warn-only
  --enable-checking=yes --enable-check-lisp-object-type=yes 'CFLAGS=-O0
  -g3 -no-pie''

Configured features:
XPM JPEG GIF PNG SOUND DBUS GSETTINGS GLIB NOTIFY INOTIFY LIBSELINUX
FREETYPE HARFBUZZ XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES
THREADS PDUMPER

Important settings:
   value of $LANG: de_AT.UTF-8
   value of $XMODIFIERS: @im=ibus
   locale-coding-system: utf-8-unix

Major mode: Lisp Interaction

Minor modes in effect:
   tooltip-mode: t
   global-eldoc-mode: t
   eldoc-mode: t
   electric-indent-mode: t
   mouse-wheel-mode: t
   tool-bar-mode: t
   menu-bar-mode: t
   file-name-shadow-mode: t
   global-font-lock-mode: t
   font-lock-mode: t
   blink-cursor-mode: t
   auto-composition-mode: t
   auto-encryption-mode: t
   auto-compression-mode: t
   line-number-mode: t
   transient-mark-mode: t

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message rmc puny dired dired-loaddefs
format-spec rfc822 mml easymenu mml-sec password-cache epa derived epg
epg-config gnus-util rmail rmail-loaddefs text-property-search time-date
subr-x seq byte-opt gv bytecomp byte-compile cconv mm-decode mm-bodies
mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader cl-loaddefs
cl-lib sendmail rfc2047 rfc2045 ietf-drums mm-util mail-prsvr mail-utils
tooltip eldoc electric uniquify ediff-hook vc-hooks lisp-float-type
mwheel term/x-win x-win term/common-win x-dnd tool-bar dnd fontset image
regexp-opt fringe tabulated-list replace newcomment text-mode elisp-mode
lisp-mode prog-mode register page tab-bar menu-bar rfn-eshadow isearch
timer select scroll-bar mouse jit-lock font-lock syntax facemenu
font-core term/tty-colors frame minibuffer cl-generic cham georgian
utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean
japanese eucjp-ms cp51932 hebrew greek romanian slovak czech european
ethiopic indian cyrillic chinese composite charscript charprop
case-table epa-hook jka-cmpr-hook help simple abbrev obarray
cl-preloaded nadvice loaddefs button faces cus-face macroexp files
text-properties overlay sha1 md5 base64 format env code-pages mule
custom widget hashtable-print-readable backquote threads dbusbind
inotify dynamic-setting system-font-setting font-render-setting
move-toolbar gtk x-toolkit x multi-tty make-network-process emacs)

Memory information:
((conses 16 43920 4887)
  (symbols 48 5978 1)
  (strings 32 15451 1816)
  (string-bytes 1 503632)
  (vectors 16 9266)
  (vector-slots 8 124434 11300)
  (floats 8 20 29)
  (intervals 56 195 0)
  (buffers 1000 11))

[-- Attachment #2: window-sizable.diff --]
[-- Type: text/x-patch, Size: 580 bytes --]

--- a/lisp/window.el
+++ b/lisp/window.el
@@ -1716,9 +1716,11 @@ window-sizable
   (setq window (window-normalize-window window))
   (cond
    ((< delta 0)
-    (max (- (window-min-size window horizontal ignore pixelwise)
-	    (window-size window horizontal pixelwise))
-	 delta))
+    (let ((min-size (window-min-size window horizontal ignore pixelwise))
+          (size (window-size window horizontal pixelwise)))
+      (if (<= size min-size)
+          0
+        (max (- min-size size) delta))))
    ((> delta 0)
     (if (window-size-fixed-p window horizontal ignore)
 	0

^ permalink raw reply	[flat|nested] 12+ messages in thread

* bug#45737: 27.1.50; Assertion failure in window_box_height
  2021-01-09  9:33 bug#45737: 27.1.50; Assertion failure in window_box_height martin rudalics
@ 2021-01-09 10:00 ` Eli Zaretskii
  2021-01-09 10:28   ` martin rudalics
  2022-02-07  1:05 ` Lars Ingebrigtsen
  1 sibling, 1 reply; 12+ messages in thread
From: Eli Zaretskii @ 2021-01-09 10:00 UTC (permalink / raw)
  To: martin rudalics; +Cc: 45737

> From: martin rudalics <rudalics@gmx.at>
> Date: Sat, 9 Jan 2021 10:33:02 +0100
> 
> (progn
>    (tab-line-mode)
>    (split-window (split-window) nil t)
>    (split-window)
>    (split-window (split-window nil nil t) nil t))
> 
> and resizing the frame by dragging its lower right corner with the mouse
> to very small rectangles I can trigger the following assertion failure:
> 
> ../../src/xdisp.c:1170: Emacs fatal error: assertion failed: height >= 0
> [...]
> Lisp Backtrace:
> "redisplay_internal (C function)" (0x0)
> (gdb) frame 2
> #2  0x0000000000458382 in window_box_height (w=0x149d100) at ../../src/xdisp.c:1170
> 1170	  eassert (height >= 0);
> (gdb) p height
> $2 = -54
> (gdb)
> 
> indicates that the total height of one of the windows dropped to -54
> pixels.  The problematic code is in 'window-sizable' which is not
> prepared for the case that window sizes can drop below their minimum
> size, something which can happen when a frame with many windows is made
> very small.  I propose the attached patch to fix this.  OK to install?

What happens in the above scenario with your patch installed?





^ permalink raw reply	[flat|nested] 12+ messages in thread

* bug#45737: 27.1.50; Assertion failure in window_box_height
  2021-01-09 10:00 ` Eli Zaretskii
@ 2021-01-09 10:28   ` martin rudalics
  2021-01-09 11:43     ` Eli Zaretskii
  0 siblings, 1 reply; 12+ messages in thread
From: martin rudalics @ 2021-01-09 10:28 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: 45737

 > What happens in the above scenario with your patch installed?

What Emacs is asking for in the scenario is to enlarge the minibuffer
window (for whatever reason, I didn't care).  With the patch installed,
Emacs won't do that but keep the minibuffer window size alone.  Note
that for the assertion failure to trigger here, the minibuffer window
must not be visible already.

All this happens in the limbo where the body size of a window exceeds
its total size, that is at least parts of a window are off-screen.
Coincidentally, I can't trigger the bug when I enable 'ruler-mode' too
so don't ask me what we are really doing here.

martin





^ permalink raw reply	[flat|nested] 12+ messages in thread

* bug#45737: 27.1.50; Assertion failure in window_box_height
  2021-01-09 10:28   ` martin rudalics
@ 2021-01-09 11:43     ` Eli Zaretskii
  2021-01-09 17:06       ` martin rudalics
  0 siblings, 1 reply; 12+ messages in thread
From: Eli Zaretskii @ 2021-01-09 11:43 UTC (permalink / raw)
  To: martin rudalics; +Cc: 45737

> Cc: 45737@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Sat, 9 Jan 2021 11:28:06 +0100
> 
>  > What happens in the above scenario with your patch installed?
> 
> What Emacs is asking for in the scenario is to enlarge the minibuffer
> window (for whatever reason, I didn't care).  With the patch installed,
> Emacs won't do that but keep the minibuffer window size alone.  Note
> that for the assertion failure to trigger here, the minibuffer window
> must not be visible already.

So the frame will resize as result dragging by mouse, but the
mini-window will not be visible?

If that is the effect, then I'm okay with installing this on emacs-27,
but I wonder whether we could do better on master, so as to ensure
that at least one screen line of the mini-window is still visible?

Btw, is this issue new in Emacs 27, or did it exist before?

Thanks.





^ permalink raw reply	[flat|nested] 12+ messages in thread

* bug#45737: 27.1.50; Assertion failure in window_box_height
  2021-01-09 11:43     ` Eli Zaretskii
@ 2021-01-09 17:06       ` martin rudalics
  2021-01-09 17:25         ` martin rudalics
  2021-01-09 17:49         ` Eli Zaretskii
  0 siblings, 2 replies; 12+ messages in thread
From: martin rudalics @ 2021-01-09 17:06 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: 45737

 > So the frame will resize as result dragging by mouse, but the
 > mini-window will not be visible?

Right.  With our gtk size hints, for example, we set

#define FRAME_TEXT_LINES_TO_PIXEL_HEIGHT(f, lines) \
   ((lines) * FRAME_LINE_HEIGHT (f)		   \
    + FRAME_TOP_MARGIN_HEIGHT (f)		   \
    + FRAME_SCROLL_BAR_HEIGHT (f)		   \
    + 2 * FRAME_INTERNAL_BORDER_WIDTH (f))

   base_height = FRAME_TEXT_LINES_TO_PIXEL_HEIGHT (f, 1)
     + FRAME_MENUBAR_HEIGHT (f) + FRAME_TOOLBAR_HEIGHT (f);

so we pretend that tab, menu and scroll bar, internal border and one
text line remain visible.  With the earlier recipe I get one text line
for the topmost normal window(s).  With

(progn
   (ruler-mode)
   (tab-line-mode)
   (horizontal-scroll-bar-mode)
   (split-window (split-window) nil t)
   (split-window)
   (split-window (split-window nil nil t) nil t))

the smallest frame shows the normal windows with a tab line and a ruler,
apparently stealing the space from the scroll bar.  The mini window
never shows up in practice.

 > If that is the effect, then I'm okay with installing this on emacs-27,
 > but I wonder whether we could do better on master, so as to ensure
 > that at least one screen line of the mini-window is still visible?

That would be better indeed.  But I suppose this would require to
implement zero-height windows, something you didn't like when we
discussed it about a year ago.

Alternatively, we (maybe) could set our size hints in a way that all
windows can be shown but maybe people wouldn't like it and on Windows
there's no way to do that without frames snapping back.

 > Btw, is this issue new in Emacs 27, or did it exist before?

New because tab lines didn't exist before Emacs 27.  And I couldn't
reproduce it with the ruler - maybe because it never wanted to write
something into the echo area.

martin





^ permalink raw reply	[flat|nested] 12+ messages in thread

* bug#45737: 27.1.50; Assertion failure in window_box_height
  2021-01-09 17:06       ` martin rudalics
@ 2021-01-09 17:25         ` martin rudalics
  2021-01-09 17:49         ` Eli Zaretskii
  1 sibling, 0 replies; 12+ messages in thread
From: martin rudalics @ 2021-01-09 17:25 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: 45737

 >    base_height = FRAME_TEXT_LINES_TO_PIXEL_HEIGHT (f, 1)
 >      + FRAME_MENUBAR_HEIGHT (f) + FRAME_TOOLBAR_HEIGHT (f);
 >
 > so we pretend that tab, menu and scroll bar, internal border and one

Obviously, I should have written "tool, menu and scroll bar" here.  We
could include the tab bar as well but so far I didn't experiment with
it.

martin





^ permalink raw reply	[flat|nested] 12+ messages in thread

* bug#45737: 27.1.50; Assertion failure in window_box_height
  2021-01-09 17:06       ` martin rudalics
  2021-01-09 17:25         ` martin rudalics
@ 2021-01-09 17:49         ` Eli Zaretskii
  2021-01-09 18:48           ` martin rudalics
  1 sibling, 1 reply; 12+ messages in thread
From: Eli Zaretskii @ 2021-01-09 17:49 UTC (permalink / raw)
  To: martin rudalics; +Cc: 45737

> Cc: 45737@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Sat, 9 Jan 2021 18:06:53 +0100
> 
>  > If that is the effect, then I'm okay with installing this on emacs-27,
>  > but I wonder whether we could do better on master, so as to ensure
>  > that at least one screen line of the mini-window is still visible?
> 
> That would be better indeed.  But I suppose this would require to
> implement zero-height windows, something you didn't like when we
> discussed it about a year ago.

Can you help me understand why this would mean zero-height windows?
What I had in mind was to constraint resizing so that the min-window
is always at least 1-line high.

In any case, please install the fix on emacs-27.





^ permalink raw reply	[flat|nested] 12+ messages in thread

* bug#45737: 27.1.50; Assertion failure in window_box_height
  2021-01-09 17:49         ` Eli Zaretskii
@ 2021-01-09 18:48           ` martin rudalics
  2021-01-09 19:02             ` Eli Zaretskii
  0 siblings, 1 reply; 12+ messages in thread
From: martin rudalics @ 2021-01-09 18:48 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: 45737

 >> That would be better indeed.  But I suppose this would require to
 >> implement zero-height windows, something you didn't like when we
 >> discussed it about a year ago.
 >
 > Can you help me understand why this would mean zero-height windows?
 > What I had in mind was to constraint resizing so that the min-window
 > is always at least 1-line high.

It depends on what you have in mind with "constraint resizing".

- We can constraint the frame size via size hints so a user can never
   make the frame smaller than needed to make all its windows visible.
   Whether this works with other window managers depends to be seen, is
   not general practice with practically all other applications I know of
   and, as mentioned before, doesn't really work on Windows.  And we
   would have to make it optional to avoid offending any users.

- Otherwise we'd have to constraint the size of normal windows since
   'window-safe-min-height' gives them always at least one frame line and
   if a frame contains two windows above each other and shrinks to two
   lines, these lines will be filled up already.  So the display engine
   and/or the windows code would have to "skip" these windows to allow
   showing the minibuffer window instead.  For me skipping a window is
   tantamount to giving it "zero height".

But maybe I'm missing something.

martin





^ permalink raw reply	[flat|nested] 12+ messages in thread

* bug#45737: 27.1.50; Assertion failure in window_box_height
  2021-01-09 18:48           ` martin rudalics
@ 2021-01-09 19:02             ` Eli Zaretskii
  2021-01-10 16:06               ` martin rudalics
  0 siblings, 1 reply; 12+ messages in thread
From: Eli Zaretskii @ 2021-01-09 19:02 UTC (permalink / raw)
  To: martin rudalics; +Cc: 45737

> Cc: 45737@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Sat, 9 Jan 2021 19:48:32 +0100
> 
>  > Can you help me understand why this would mean zero-height windows?
>  > What I had in mind was to constraint resizing so that the min-window
>  > is always at least 1-line high.
> 
> It depends on what you have in mind with "constraint resizing".
> 
> - We can constraint the frame size via size hints so a user can never
>    make the frame smaller than needed to make all its windows visible.
>    Whether this works with other window managers depends to be seen, is
>    not general practice with practically all other applications I know of
>    and, as mentioned before, doesn't really work on Windows.  And we
>    would have to make it optional to avoid offending any users.
> 
> - Otherwise we'd have to constraint the size of normal windows since
>    'window-safe-min-height' gives them always at least one frame line and
>    if a frame contains two windows above each other and shrinks to two
>    lines, these lines will be filled up already.  So the display engine
>    and/or the windows code would have to "skip" these windows to allow
>    showing the minibuffer window instead.  For me skipping a window is
>    tantamount to giving it "zero height".

I'm okay with the frame resetting itself back to a safe size, if the
WM cannot be hinted.  The main point is not to reduce the frame size
to dimensions that don't allow us to keep a mini-window of at least
one line.





^ permalink raw reply	[flat|nested] 12+ messages in thread

* bug#45737: 27.1.50; Assertion failure in window_box_height
  2021-01-09 19:02             ` Eli Zaretskii
@ 2021-01-10 16:06               ` martin rudalics
  0 siblings, 0 replies; 12+ messages in thread
From: martin rudalics @ 2021-01-10 16:06 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: 45737

 > I'm okay with the frame resetting itself back to a safe size, if the
 > WM cannot be hinted.

We can try to hint the WM and even make that the default.  But this
won't help people on tiling WMs or embedded frames.  And a WM that
cannot be hinted might just size the frame back as well.  We had some
issues with GNOME shell in the past and with pgtk/Wayland most of our
desires to control screen layout will have become a pipe dream anyway.

 > The main point is not to reduce the frame size
 > to dimensions that don't allow us to keep a mini-window of at least
 > one line.

It depends on what _we_ want to show above that line.  The screen estate
within the native frame rectangle is and will stay with us forever.

martin





^ permalink raw reply	[flat|nested] 12+ messages in thread

* bug#45737: 27.1.50; Assertion failure in window_box_height
  2021-01-09  9:33 bug#45737: 27.1.50; Assertion failure in window_box_height martin rudalics
  2021-01-09 10:00 ` Eli Zaretskii
@ 2022-02-07  1:05 ` Lars Ingebrigtsen
  2022-02-07  8:57   ` martin rudalics
  1 sibling, 1 reply; 12+ messages in thread
From: Lars Ingebrigtsen @ 2022-02-07  1:05 UTC (permalink / raw)
  To: martin rudalics; +Cc: 45737

martin rudalics <rudalics@gmx.at> writes:

> With the current release version running emacs -Q, evaluating
>
> (progn
>   (tab-line-mode)
>   (split-window (split-window) nil t)
>   (split-window)
>   (split-window (split-window nil nil t) nil t))
>
> and resizing the frame by dragging its lower right corner with the mouse
> to very small rectangles I can trigger the following assertion failure:
>
> ../../src/xdisp.c:1170: Emacs fatal error: assertion failed: height >= 0

I'm unable to reproduce this in Emacs 29 on Debian/bookworm.  But it
does spew out a lot of these warnings:

emacs:609181): Gtk-CRITICAL **: 02:04:10.529: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





^ permalink raw reply	[flat|nested] 12+ messages in thread

* bug#45737: 27.1.50; Assertion failure in window_box_height
  2022-02-07  1:05 ` Lars Ingebrigtsen
@ 2022-02-07  8:57   ` martin rudalics
  0 siblings, 0 replies; 12+ messages in thread
From: martin rudalics @ 2022-02-07  8:57 UTC (permalink / raw)
  To: Lars Ingebrigtsen; +Cc: 45737

close 45737 27.1
quit

 > I'm unable to reproduce this in Emacs 29 on Debian/bookworm.

Good.  I (hopefully) closed that bug now.

 > But it
 > does spew out a lot of these warnings:
 >
 > emacs:609181): Gtk-CRITICAL **: 02:04:10.529: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed

That's either the GTK menu or tool bar.  Try with them disabled.

martin





^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2022-02-07  8:57 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-09  9:33 bug#45737: 27.1.50; Assertion failure in window_box_height martin rudalics
2021-01-09 10:00 ` Eli Zaretskii
2021-01-09 10:28   ` martin rudalics
2021-01-09 11:43     ` Eli Zaretskii
2021-01-09 17:06       ` martin rudalics
2021-01-09 17:25         ` martin rudalics
2021-01-09 17:49         ` Eli Zaretskii
2021-01-09 18:48           ` martin rudalics
2021-01-09 19:02             ` Eli Zaretskii
2021-01-10 16:06               ` martin rudalics
2022-02-07  1:05 ` Lars Ingebrigtsen
2022-02-07  8:57   ` martin rudalics

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).