From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: 25875@debbugs.gnu.org
Subject: bug#25875: 26.0.50; Hang logging out of MS-Windows
Date: Tue, 28 Feb 2017 17:36:02 +0200 [thread overview]
Message-ID: <834lzepbtp.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58ohNqEpHdUdFNNKD5KhGgbNxeeND160gX15Et9V6g=rTNg@mail.gmail.com> (message from Richard Copley on Tue, 28 Feb 2017 07:21:04 +0000)
> From: Richard Copley <rcopley@gmail.com>
> Date: Tue, 28 Feb 2017 07:21:04 +0000
> Cc: Ken Brown <kbrown@cornell.edu>, 25875@debbugs.gnu.org
>
> > How representative would the above sample be, relative to the
> > frequency of the problem you see when shutting down Windows? If you
> > see such problems almost every shutdown, then yes, we'd be learning a
> > lot.
>
> In the nine months since Ken's change, I've noticed a problem with
> Emacs twice.
Then I guess it would be better to just push those changes and see if
they do any harm.
> Ken, Eli, are you going to be running Emacs with that patch installed?
I never use the master branch for serious work, so it doesn't matter
what I do. In addition, I almost never shut down my systems.
> I can't get my head around the idea. If we don't care whether or not
> the action in question has finished when SendMessage returns,
> then why are we using SendMessage? And if we do care, then
> shouldn't I expect weird bugs caused by timing out when the system's
> under load?
If a window procedure doesn't process messages for more than 5 sec,
Windows will put "Not Responding" on its caption bar. So I think the
100 msec number in Ken's patch should be changed to something like
6000, and then we are fine, because even on a busy system this should
be long enough. And if Emacs (and the OS) is about to shut down, it's
even less of a problem to ignore a message that timed out, IMO.
next prev parent reply other threads:[~2017-02-28 15:36 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 19:35 bug#25875: 26.0.50; Hang logging out of MS-Windows Richard Copley
2017-02-25 19:41 ` Richard Copley
2017-02-25 20:36 ` Eli Zaretskii
2017-02-25 21:13 ` Richard Copley
2017-02-26 15:47 ` Eli Zaretskii
2017-02-26 18:26 ` Richard Copley
2017-02-25 20:33 ` Eli Zaretskii
2017-02-25 21:07 ` Richard Copley
2017-02-25 21:30 ` Richard Copley
2017-02-25 21:37 ` Richard Copley
2017-02-25 22:02 ` Richard Copley
2017-02-26 15:47 ` Eli Zaretskii
2017-02-26 18:37 ` Richard Copley
2017-02-26 15:44 ` Eli Zaretskii
2017-02-26 18:04 ` Ken Brown
2017-02-26 18:25 ` Eli Zaretskii
2017-02-26 18:58 ` Ken Brown
2017-02-26 19:25 ` Eli Zaretskii
2017-02-26 23:38 ` Ken Brown
2017-02-27 8:14 ` Richard Copley
2017-02-27 15:36 ` Eli Zaretskii
2017-02-27 19:04 ` Richard Copley
2017-02-27 19:16 ` Eli Zaretskii
2017-02-27 19:23 ` Richard Copley
2017-02-27 19:30 ` Richard Copley
2017-02-27 19:39 ` Ken Brown
2017-02-27 19:46 ` Richard Copley
2017-02-27 19:56 ` Richard Copley
2017-02-27 20:19 ` Ken Brown
2017-02-27 20:27 ` Eli Zaretskii
2017-02-27 20:52 ` Richard Copley
2017-02-27 20:58 ` Eli Zaretskii
2017-02-27 21:09 ` Richard Copley
2017-02-28 3:30 ` Eli Zaretskii
2017-02-28 6:37 ` Richard Copley
2017-02-27 22:37 ` Ken Brown
2017-02-27 23:03 ` Richard Copley
2017-02-28 3:35 ` Eli Zaretskii
2017-02-28 7:21 ` Richard Copley
2017-02-28 15:36 ` Eli Zaretskii [this message]
2017-02-28 16:40 ` Ken Brown
2017-02-28 16:44 ` Eli Zaretskii
2017-02-28 18:59 ` Richard Copley
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=834lzepbtp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25875@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).