From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Parser cache is disabled by default Date: Sun, 22 Jan 2017 00:16:48 +0100 Message-ID: <877f5oc8bj.fsf@nicolasgoaziou.fr> References: <87tw8sd9qo.fsf@nicolasgoaziou.fr> <20170121124330.kspplgwnpert64zc@len.workgroup> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53448) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cV4u0-00023P-IL for emacs-orgmode@gnu.org; Sat, 21 Jan 2017 18:16:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cV4tz-0006no-Mq for emacs-orgmode@gnu.org; Sat, 21 Jan 2017 18:16:56 -0500 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:55154) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cV4tz-0006nU-GX for emacs-orgmode@gnu.org; Sat, 21 Jan 2017 18:16:55 -0500 Received: from saiph.selenimh (00004301000000000000074b.ipv6.commingeshautdebit.fr [IPv6:2a03:a0a0:0:4301::74b]) (Authenticated sender: mail@nicolasgoaziou.fr) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 0E3F3A80C2 for ; Sun, 22 Jan 2017 00:16:53 +0100 (CET) Received: from ngz by saiph.selenimh with local (Exim 4.88) (envelope-from ) id 1cV4ts-00038u-EC for emacs-orgmode@gnu.org; Sun, 22 Jan 2017 00:16:48 +0100 In-Reply-To: <20170121124330.kspplgwnpert64zc@len.workgroup> (Gregor Zattler's message of "Sat, 21 Jan 2017 13:43:30 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode Hello, Gregor Zattler writes: > Is there an easy to follow receipt what to do in order to help > you debugging? When Emacs hangs I do pkill -USR2 emacs but then > there is no debug info!? The freezes itself is easy to understand. The cache (an AVL tree) is corrupted, and inserting a new cached object infloops, roughly. Debugging data obtained at the time of the freeze is probably not useful. The difficult part is to find an ECM to reproduce the bug. AFAIU, headlines are involved, probably in conjunction with property drawers. Unfortunately, you may only realize the cache is corrupted quite some time after it happened. Typically, you are close to getting a recipe when you experience a freeze, reset the cache (`org-element-cache-reset'), resume working and quickly experience another freeze. The ingredients are between the reset and the new freeze. Regards, -- Nicolas Goaziou