unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 38038@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
	Juri Linkov <juri@linkov.net>
Subject: bug#38038: 27.0.50; Emacs freezes opening tabs.
Date: Fri, 8 Nov 2019 22:39:38 +0100	[thread overview]
Message-ID: <20191108213938.lp5yt753fszjrroe@Ergus> (raw)
In-Reply-To: <5455d765-4954-6bc0-1961-619f6e865f59@gmx.at>

On Fri, Nov 08, 2019 at 10:21:14AM +0100, martin rudalics wrote:
>> These hangs occur not only with tab-bar, but also with menu-bar
>> when tab-bar is not enabled.  These hangs can be reproduced by
>> configuring --with-x-toolkit=no and running emacs -Q.
>> Then evaluating this causes hangs:
>>
>>    (set-face-attribute 'menu nil :weight 'ultra-bold :underline t)
>
>On Windows
>
>(set-face-attribute 'default nil :underline t)
>
>suffices to make it hang in the tool bar redisplay code.  I have the
>guts feeling that it's related to the new :extend mechanism because it
>works in Emacs 26.
>
>martin

Hi Martin:

I will try a simple check to test if it is relates commenting the call
to merge in extend_face_to_end_of_line. But I don't see it related at
all; the loop seems to be in some gc functions. Remember that the gc has
been changes too since emacs 26.






  reply	other threads:[~2019-11-08 21:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191102214135.lehpefr5o4cji6ca.ref@Ergus>
2019-11-02 21:41 ` bug#38038: 27.0.50; Emacs freezes opening tabs Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-11-02 22:20   ` Juri Linkov
2019-11-02 22:55     ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-11-03 20:22       ` Juri Linkov
2019-11-07 14:01     ` Eli Zaretskii
2019-11-07 14:50       ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-11-07 22:36       ` Juri Linkov
2019-11-08  9:21         ` martin rudalics
2019-11-08 21:39           ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2019-11-08 23:08           ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-11-09  8:09             ` martin rudalics
2019-11-09  8:28               ` Eli Zaretskii
2019-11-09  9:02                 ` martin rudalics
2019-11-09  9:25                   ` Eli Zaretskii
2019-11-10  9:45                     ` martin rudalics
2019-11-12  0:39                       ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-11-12  8:10                         ` martin rudalics
2019-11-12 12:20                           ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-11-12 15:48                             ` martin rudalics

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191108213938.lp5yt753fszjrroe@Ergus \
    --to=bug-gnu-emacs@gnu.org \
    --cc=38038@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    --cc=rudalics@gmx.at \
    --cc=spacibba@aol.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).