public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: cygwin@cygwin.com
Subject: Re: A workaround against Emacs crash when displaying images
Date: Fri, 08 Mar 2019 12:05:00 -0000	[thread overview]
Message-ID: <20190308120440.GG3785@calimero.vinschen.de> (raw)
In-Reply-To: <b4m8sxqdlu7.fsf@jpl.org>

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

On Mar  8 13:36, Katsumi Yamaoka wrote:
> On Fri, 08 Mar 2019 08:36:24 +0900, Katsumi Yamaoka wrote:
> > I tried the 2019-03-06 snapshot and, oh!, I verified Emacs got
> > not to crash for displaying images without such a spell.
> > It seems Emacs revived as for me as it was before Cygwin 3.
> 
> I'm sorry that was a hasty conclusion.  Emacs suddenly freezes when
> I am typing somthing even if it is simply a text that will never
> change frame or window configuration nor displaying image; happens
> with Cygwin's Emacs and the ones I built from git; neither C-g nor
> `kill -9' doesn't help; killing it using the Windows task manager
> is the only measure to stop it.  As it makes me hard to work, I
> reverted the use of the snapshot to 3.0.2.

I could reproduce the hang and found a potential deadlock situation.
I pushed a fix and uploaded new developer snapshots to
https://cygwin.com/snapshots/

Please test.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-03-08 12:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07  0:20 Katsumi Yamaoka
2019-03-07 15:55 ` Ken Brown
2019-03-07 23:36   ` Katsumi Yamaoka
2019-03-08  4:36     ` Katsumi Yamaoka
2019-03-08 12:05       ` Corinna Vinschen [this message]
2019-03-10 23:12         ` Katsumi Yamaoka

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

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

  git send-email \
    --in-reply-to=20190308120440.GG3785@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    --cc=yamaoka@jpl.org \
    /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.
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).