From: Austin Bingham <austin.bingham@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Help understanding some bad emacs behavior
Date: Sun, 16 Nov 2014 21:32:49 +0000 [thread overview]
Message-ID: <CAEZidR0Qz48jPzOeFoBSe7amdB8Z99Y3Yyj6p21RYSRrpDyL2A@mail.gmail.com> (raw)
In-Reply-To: jwvegt3sz8t.fsf-monnier+emacs@gnu.org
[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]
On Sun Nov 16 2014 at 1:53:20 PM Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> > I'm working on some code-completion related packages (company + ycmd),
> and
> > something I'm doing is triggering some pathological behavior that I could
> > use help on.
>
> Care to describe what is this pathological behavior you're seeing?
>
Sorry, good point. The emacs process maxes out one of my cores for a few
minutes. During this time emacs seems unresponsive to input, though it does
redraw on the screen.
> > Under some conditions that I haven't fully characterized yet, a thread
> > in emacs goes off on an extended, recursive-looking adventure of
> > some sort.
>
> What makes you think so?
>
The stack trace. It's clearly doing some recursion, though whether that
actually has any bearing on the behavior I'm seeing is just conjecture.
Maybe the deep-seeming stack of Ffuncall/exec_byte_code/etc. is normal, but
it was remarkable enough to me that I thought I'd mention it.
> What I'm hoping is that someone on this list can look at the
> > attached stack info and give me some hint as to what might be going on.
>
> Better show the Elisp backtrace rather than the C backtrace.
>
What's the best way to get that? Bear in mind that, as far as I can tell,
emacs isn't responding to input when I see this problem. And since I don't
really know where this is happening in elisp-land, I'm not sure where to
add instrumentation or anything like that.
Austin
[-- Attachment #2: Type: text/html, Size: 2130 bytes --]
next prev parent reply other threads:[~2014-11-16 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 13:09 Help understanding some bad emacs behavior Austin Bingham
2014-11-16 19:53 ` Stefan Monnier
2014-11-16 21:32 ` Austin Bingham [this message]
2014-11-17 2:10 ` Stefan Monnier
2014-11-17 15:58 ` Austin Bingham
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=CAEZidR0Qz48jPzOeFoBSe7amdB8Z99Y3Yyj6p21RYSRrpDyL2A@mail.gmail.com \
--to=austin.bingham@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).