From: Keith David Bershatsky <esq@lawlist.com>
To: Emacs Devel <emacs-devel@gnu.org>
Subject: NS port: How to debug excessive garbage collection?
Date: Wed, 10 Apr 2019 20:27:49 -0700 [thread overview]
Message-ID: <m2ef69p6fe.wl%esq@lawlist.com> (raw)
I am working on feature requests 22873 (multiple fake cursors) and 17684 (crosshairs that track the cursor position).
On 04/08/2019, I submitted a proof concept patch to the following bug tracker link that applies to a current version of the master branch as of that date/commit. It works for GUI versions of Emacs on w32, X11 and NS ports:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22873#125
The bulk of my daily workflow is performed on a modified earlier version of the Emacs master branch from 03/28/2016, which uses about 98% of a current version of the display engine (xdisp.c) as of 04/08/2019. The proof concept patches for each version of Emacs (03/28/2016 versus 04/08/2019) are virtually identical. The only major difference is that nsterm.m has undergone significant changes over the past few months to accommodate Mojave users (MacOS).
Here is a Youtube link to a screen recording of the 03/28/2016 version of Emacs NS port -- there are virtually no visual pauses whatsoever while I hold down the right arrow key:
https://youtu.be/4vTX1YwrfC4
Here is a Youtube link to a screen recording of the 04/08/2019 version of Emacs NS port -- there is a painfully noticeable pause every few characters while I hold down the right arrow key:
https://youtu.be/RzkB4HKHR6o
The painful garbage collection issues do _not_ plague either the w32 port or the X11 port of Emacs master branch as of 04/08/2019.
Q: How should I proceed to debug the excessive garbage collection issue on the NS port?
Thanks,
Keith
next reply other threads:[~2019-04-11 3:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 3:27 Keith David Bershatsky [this message]
2019-04-11 14:14 ` NS port: How to debug excessive garbage collection? Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2019-04-11 23:04 Keith David Bershatsky
2019-04-12 9:30 ` Eli Zaretskii
2019-04-13 5:55 Keith David Bershatsky
2019-04-13 6:48 ` Eli Zaretskii
2019-04-13 16:31 Keith David Bershatsky
2019-04-13 17:02 ` Alex Gramiak
2019-04-13 18:07 Keith David Bershatsky
2019-04-13 21:41 ` Alex Gramiak
2019-04-14 3:47 ` Daniel Colascione
2019-04-14 7:41 Keith David Bershatsky
2019-04-14 19:46 Keith David Bershatsky
2019-04-14 23:31 ` Alex Gramiak
2019-04-15 2:55 Keith David Bershatsky
2019-04-15 3:44 ` Alex Gramiak
2019-04-15 5:19 Keith David Bershatsky
2019-04-16 2:57 Keith David Bershatsky
2019-04-16 5:26 ` Alex Gramiak
2019-04-16 5:51 Keith David Bershatsky
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=m2ef69p6fe.wl%esq@lawlist.com \
--to=esq@lawlist.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.