From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Austin Bingham Newsgroups: gmane.emacs.devel Subject: Re: Help understanding some bad emacs behavior Date: Sun, 16 Nov 2014 21:32:49 +0000 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b5d46068efaeb0508009afd X-Trace: ger.gmane.org 1416174340 19514 80.91.229.3 (16 Nov 2014 21:45:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 16 Nov 2014 21:45:40 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 16 22:45:34 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Xq7dU-0001CK-JA for ged-emacs-devel@m.gmane.org; Sun, 16 Nov 2014 22:45:32 +0100 Original-Received: from localhost ([::1]:45166 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xq7dT-0000UU-T3 for ged-emacs-devel@m.gmane.org; Sun, 16 Nov 2014 16:45:32 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38401) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xq7RD-0008Ai-Cu for emacs-devel@gnu.org; Sun, 16 Nov 2014 16:32:52 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xq7RC-0002Kc-7V for emacs-devel@gnu.org; Sun, 16 Nov 2014 16:32:51 -0500 Original-Received: from mail-yh0-x22d.google.com ([2607:f8b0:4002:c01::22d]:33520) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xq7RC-0002KW-38 for emacs-devel@gnu.org; Sun, 16 Nov 2014 16:32:50 -0500 Original-Received: by mail-yh0-f45.google.com with SMTP id f10so3440559yha.18 for ; Sun, 16 Nov 2014 13:32:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:from:date:message-id:subject:to:cc :content-type; bh=1SwPwLCAj1oyhCPIjaC8lRRwoINLyEnKCAUcYnCY0tE=; b=ZH2XyZvRR65A8yblplH52ms5OCvqh4/peFmb26PjpMx9vFgMfjYDpw483/J+0s0hRZ bYlJeIQDKUQRH7JF9DnGScRKhnrxp7LYAdKTtkY9gqhLJ/ApxADSnK2rsZX+ON+3TSC9 KYRtoJKKSkVJRDBnxk4I2AXnlXEexV3cxdXihGWGb8tp3K2U+L+E4dRDt1XR24/ytdu0 8tkoVGjNfHSVQIsHqQZOCOuaC4b5PWbegRHVp698L0nCj2QG9Osx8XUicJBxpiBiXddI z+V4OXryFFOBvlcz+wGksxuyEiQ1cWtoXjG+LW2ezXB+n8d6lofjuXfTW2aoHWQH9lGQ Y+4Q== X-Received: by 10.236.26.179 with SMTP id c39mr21365931yha.7.1416173569634; Sun, 16 Nov 2014 13:32:49 -0800 (PST) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4002:c01::22d X-Mailman-Approved-At: Sun, 16 Nov 2014 16:45:26 -0500 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:177363 Archived-At: --047d7b5d46068efaeb0508009afd Content-Type: text/plain; charset=UTF-8 On Sun Nov 16 2014 at 1:53:20 PM Stefan Monnier 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 --047d7b5d46068efaeb0508009afd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Sun Nov 16 2014 at 1:53:20 PM Stefan = Monnier <monnier@iro.umontre= al.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?
<= /blockquote>

Sorry, good point. The emacs process maxes = out one of my cores for a few minutes. During this time emacs seems unrespo= nsive to input, though it does redraw on the screen.
=C2=A0
=
> Under some conditions that I haven't fully characterized yet, a th= read
> in emacs goes off on an extended, recursive-looking adventure of
> some sort.

What makes you think so?

The stack trac= e. It's clearly doing some recursion, though whether that actually has = any bearing on the behavior I'm seeing is just conjecture. Maybe the de= ep-seeming stack of Ffuncall/exec_byte_code/etc. is normal, but =C2=A0it wa= s 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.
=C2=A0
What's the best way to get that? Bear in mind t= hat, as far as I can tell, emacs isn't responding to input when I see t= his problem. And since I don't really know where this is happening in e= lisp-land, I'm not sure where to add instrumentation or anything like t= hat.

Austin
--047d7b5d46068efaeb0508009afd--