From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Alexander Shukaev <emacs@Alexander.Shukaev.name>
Cc: 29095@debbugs.gnu.org
Subject: bug#29095: Bug: The '20a09de953f437109a098fa8c4d380663d921481' merge increased my Emacs configuration loading time from 9 s to 60 s
Date: Wed, 01 Nov 2017 20:21:13 -0400 [thread overview]
Message-ID: <87zi858r9i.fsf@users.sourceforge.net> (raw)
In-Reply-To: <d633ff32-ea4c-659b-52a0-033a6a4042e3@Alexander.Shukaev.name> (Alexander Shukaev's message of "Thu, 2 Nov 2017 00:49:28 +0100")
Alexander Shukaev <emacs@Alexander.Shukaev.name> writes:
>> I know what you mean by "which is unacceptable", but somehow on first
>> reading it strikes me as rather bossy and entitled.
>
> Apologies, didn't want it to sound like that.
Indeed, I didn't really think so. But I've been thinking a lot about
how to avoid threads which devolve into bitter sniping (which is more
common than I'd like in emacs-devel/bugs), and I think calling such
things out at the beginning could help avoid misunderstandings.
> As my original findings (namely merge commit from the 'emacs-26'
> branch) demonstrated, there is no stable branch at the moment as the
> faulty commit is now present in both. In fact, the 'emacs-26' was
> merged to master (and not vice versa), so it's the issue that came
> from what you call a "stable" branch. This is another surprise for
> me.
In this context, "stable" just means no features are getting added.
Ideally no bugs either, but sometimes bug fixes end up adding bugs too.
> And that's what I just finished doing, voilà:
>
> e1f6e3127a292e6ba66d27c49ddda4fe949569f5
> Author: Noam Postavsky
> AuthorDate: Wed Aug 30 23:12:22 2017 -0400
Hah! It was me ;)
> And yes, of course, as soon as I found this by spending a couple of
> hours more doing bisecting, I did immediately set
> `x-wait-for-event-timeout' to nil and the startup problem was
> gone. However, I'm still gravely concerned that such defaults (100 ms
> GUI delays) suddenly get added (whatever the reason for this new
> option was) and affect both branches.
Versions 25.3 and lower all had this wait, and removing it cause some
problems for other users (see Bug#25521 and Bug#25511). Therefore it
was restored in emacs-26 (and (almost) everything in emacs-26 goes to
master) with the option to remove it. In fact, the wait used to be
unbounded, so a timeout is something of a compromise.
What confuses me though, is how a 100ms delay is adding ~50s to your
starup time?! Or are you just creating 500 frames on startup?
> As the output from the build kept arriving to the *compilation*
> buffer, I kept getting "Garbage collecting...done" spam (at random
> times), stuttering the output coming into *compilation* buffer. You
> don't have to explain to me here anything about GC, I am well aware of
> all of these issues.
Just to clarify, you have garbage-collection-messages set to non-nil on
purpose?
next prev parent reply other threads:[~2017-11-02 0:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 0:44 bug#29095: Bug: The '20a09de953f437109a098fa8c4d380663d921481' merge increased my Emacs configuration loading time from 9 s to 60 s Alexander Shukaev
2017-11-01 1:31 ` Noam Postavsky
2017-11-01 23:49 ` Alexander Shukaev
2017-11-02 0:21 ` Noam Postavsky [this message]
2017-11-04 23:28 ` Alexander Shukaev
2017-11-04 23:53 ` Noam Postavsky
2017-11-04 23:58 ` Alexander Shukaev
2017-11-05 10:53 ` martin rudalics
2017-11-07 9:10 ` Noam Postavsky
2017-11-07 12:57 ` Noam Postavsky
2017-11-08 7:13 ` martin rudalics
2017-11-08 13:42 ` Noam Postavsky
2017-11-09 7:28 ` martin rudalics
2017-11-09 13:20 ` Noam Postavsky
2017-11-09 18:12 ` martin rudalics
2017-11-09 22:09 ` Alexander Shukaev
2017-11-09 22:22 ` Alexander Shukaev
2017-11-10 0:53 ` Noam Postavsky
2019-04-23 2:52 ` Noam Postavsky
2017-11-12 10:09 ` martin rudalics
2017-11-08 7:13 ` martin rudalics
2017-11-01 3:44 ` 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=87zi858r9i.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=29095@debbugs.gnu.org \
--cc=emacs@Alexander.Shukaev.name \
/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).