From: Eli Zaretskii <eliz@gnu.org>
To: Robert Vojta <rvojta@me.com>
Cc: 26980@debbugs.gnu.org
Subject: bug#26980: 25.2; Freeze & redisplay_internal & macOS
Date: Thu, 18 May 2017 18:02:55 +0300 [thread overview]
Message-ID: <831srm5hsw.fsf@gnu.org> (raw)
In-Reply-To: <299A4BDA-DCE3-4561-8841-468EA6FD655C@me.com> (message from Robert Vojta on Thu, 18 May 2017 07:57:04 +0200)
> From: Robert Vojta <rvojta@me.com>
> Date: Thu, 18 May 2017 07:57:04 +0200
>
> What I was doing when it freezes?
>
> * Scroll with mouse wheel
> * Refactor namespace
> * Simple typing clj code
> * Git fetch
>
> As you can see, basically whatever can trigger this issue.
>
> SIGUSR2 generates backtrace and it always ends up in redisplay_internal. Example:
>
> > Debugger entered--Lisp error: (quit)
> > redisplay_internal\ \(C\ function\)()
>
> Another example:
>
> > Debugger entered--entering a function:
> > * command-error-default-function((quit) "" nil)
> > recursive-edit()
> > debug(error (quit))
> > ...
> > linum-after-scroll(#<window 3 on *Backtrace*> 2215)
> > redisplay_internal\ \(C\ function\)()
>
> Would like to solve this issue, but don’t know how. What else I can provide to make this report more useful?
Please attach GDB to a freezing Emacs and show the C-level backtrace.
That will show more information, specifically below
redisplay_internal.
next prev parent reply other threads:[~2017-05-18 15:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 5:57 bug#26980: 25.2; Freeze & redisplay_internal & macOS Robert Vojta
2017-05-18 15:02 ` Eli Zaretskii [this message]
2017-05-19 10:27 ` Robert Vojta
2017-05-19 11:20 ` Eli Zaretskii
2017-05-19 11:40 ` Robert Vojta
2017-05-25 16:59 ` Robert Vojta
2017-05-26 10:38 ` Robert Vojta
2017-05-26 11:01 ` Robert Vojta
2017-05-26 19:44 ` Eli Zaretskii
2017-05-29 9:37 ` Robert Vojta
2017-05-30 7:46 ` Eli Zaretskii
2017-05-30 8:02 ` Robert Vojta
2017-05-30 8:33 ` Eli Zaretskii
2019-09-29 15:06 ` Lars Ingebrigtsen
2019-10-14 7:33 ` Lars Ingebrigtsen
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=831srm5hsw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26980@debbugs.gnu.org \
--cc=rvojta@me.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).