unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rcopley@gmail.com
Cc: 25279@debbugs.gnu.org
Subject: bug#25279: 26.0.50; Slowdown/crash on certain characters
Date: Thu, 23 Feb 2017 18:19:44 +0200	[thread overview]
Message-ID: <8337f4ubfj.fsf@gnu.org> (raw)
In-Reply-To: <83h93nthka.fsf@gnu.org> (message from Eli Zaretskii on Tue, 21 Feb 2017 22:28:05 +0200)

> Date: Tue, 21 Feb 2017 22:28:05 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 25279@debbugs.gnu.org
> 
> > From: Richard Copley <rcopley@gmail.com>
> > Date: Tue, 21 Feb 2017 20:05:28 +0000
> > Cc: 25279@debbugs.gnu.org
> > 
> > Here's how to make Emacs hang without the need to uninstall any fonts,
> > on Windows (not reproducible on GNU/Linux).
> > 1. Type "M-x view-hello-file" (don't press return).
> > 2. In quick succession, type "C-m" and then "C-g". *
> 
> Thanks.
> 
> > Eli, should I retitle this bug to "26.0.50; calling SendMessage inside
> > critical section causes deadlock", or close this bug as a duplicate of
> > the other "slow fonts on Windows" bugs and file a new report about
> > the hanging?
> 
> The former, I guess.  I will take a look when I have time.

I think I found the reason: due to C-g, we were jumping to top-level
while in a critical section, which is a very bad idea, because any
non-main thread that tries to acquire the critical section after that
will necessarily hang.

Please try the latest master and see if any such hangs are still
there.

Thanks for the recipe, it made it quite easy to catch the villain
red-handed.





  parent reply	other threads:[~2017-02-23 16:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-26 20:09 bug#25279: 26.0.50; Slowdown/crash on certain characters Richard Copley
2016-12-26 20:18 ` Richard Copley
2016-12-26 20:25 ` Eli Zaretskii
2016-12-26 20:40   ` Richard Copley
2016-12-26 20:49     ` Eli Zaretskii
2016-12-26 21:21       ` Richard Copley
2016-12-27  7:21         ` Eli Zaretskii
     [not found]           ` <CAPM58oiS8+TuR8WhKZmEZdWY_ac44xLDjnpYAD0aWqU6=mX7eg@mail.gmail.com>
2016-12-27 13:51             ` bug#25279: Fwd: " Richard Copley
     [not found]             ` <CAPM58oioMPAo=x8F1whs5YS3RMwceoadAT9TN7Macbx=SaxyJA@mail.gmail.com>
2016-12-27 13:53               ` Richard Copley
     [not found]               ` <838tr1wlg4.fsf@gnu.org>
     [not found]                 ` <CAPM58og6d1EqTEyMy6df27DXB_ERYOD5=pmFHC9MmoFmq+CDgw@mail.gmail.com>
     [not found]                   ` <837f6lwkju.fsf@gnu.org>
2016-12-27 14:06                     ` Richard Copley
2016-12-27 14:15                       ` Eli Zaretskii
2016-12-27 14:32                         ` Richard Copley
2016-12-27 21:15                           ` Richard Copley
2017-02-21 20:05                             ` Richard Copley
2017-02-21 20:28                               ` Eli Zaretskii
2017-02-21 20:33                                 ` Richard Copley
2017-02-21 20:38                                   ` Richard Copley
2017-02-23 16:19                                 ` Eli Zaretskii [this message]
2017-02-23 19:15                                   ` Richard Copley
2017-02-23 19:20                                     ` Richard Copley
2017-02-23 15:22                               ` Eli Zaretskii

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=8337f4ubfj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=25279@debbugs.gnu.org \
    --cc=rcopley@gmail.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).