[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#17975: 24.3.92; assertion failure deleting frames with varying names
From: |
Dmitry Antipov |
Subject: |
bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too) |
Date: |
Sun, 13 Jul 2014 19:54:15 +0400 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
On 07/13/2014 07:04 PM, Eli Zaretskii wrote:
Does it help to avoid calling update_menu_bar for frames that don't
pass the FRAME_LIVE_P test?
If you mean just this:
=== modified file 'src/xdisp.c'
--- src/xdisp.c 2014-07-12 17:53:29 +0000
+++ src/xdisp.c 2014-07-13 15:32:01 +0000
@@ -11698,7 +11698,8 @@
}
GCPRO1 (tail);
- menu_bar_hooks_run = update_menu_bar (f, 0, menu_bar_hooks_run);
+ if (FRAME_LIVE_P (f))
+ menu_bar_hooks_run = update_menu_bar (f, 0, menu_bar_hooks_run);
#ifdef HAVE_WINDOW_SYSTEM
update_tool_bar (f, 0);
#endif
then no, at least for Ken's test case.
Dmitry
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Ken Raeburn, 2014/07/08
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Dmitry Antipov, 2014/07/10
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Ken Raeburn, 2014/07/11
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Dmitry Antipov, 2014/07/13
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Dmitry Antipov, 2014/07/13
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Dmitry Antipov, 2014/07/13
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Eli Zaretskii, 2014/07/13
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too),
Dmitry Antipov <=
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Eli Zaretskii, 2014/07/13
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Dmitry Antipov, 2014/07/13
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Eli Zaretskii, 2014/07/13
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Dmitry Antipov, 2014/07/14
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Ken Raeburn, 2014/07/14
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Dmitry Antipov, 2014/07/14
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Jan Djärv, 2014/07/14
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Dmitry Antipov, 2014/07/14
- bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too), Ken Raeburn, 2014/07/14