From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: C-c C-c in table takes 12 seconds Date: Sun, 23 Nov 2014 19:14:10 +0100 Message-ID: <87mw7h6az1.fsf@gmx.us> References: <2014-11-23T13-27-20@devnull.Karl-Voit.at> <2014-11-23T13-45-08@devnull.Karl-Voit.at> <87y4r13lce.fsf@nicolasgoaziou.fr> <877fyl7sla.fsf@gmx.us> <87lhn13ibr.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54485) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xsbgm-0006bC-Ca for emacs-orgmode@gnu.org; Sun, 23 Nov 2014 13:15:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xsbgg-0003pa-UA for emacs-orgmode@gnu.org; Sun, 23 Nov 2014 13:15:12 -0500 Received: from plane.gmane.org ([80.91.229.3]:44750) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xsbgg-0003ok-NL for emacs-orgmode@gnu.org; Sun, 23 Nov 2014 13:15:06 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Xsbge-0005qx-Hy for emacs-orgmode@gnu.org; Sun, 23 Nov 2014 19:15:04 +0100 Received: from 168.96.135.37.dynamic.jazztel.es ([37.135.96.168]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 23 Nov 2014 19:15:04 +0100 Received: from rasmus by 168.96.135.37.dynamic.jazztel.es with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 23 Nov 2014 19:15:04 +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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hi, Nicolas Goaziou writes: > Rasmus writes: > >> When looking at the profiler, I notice avl-tree--do-delete (and other >> avl functions) and org-element--cache-compare taking lots of speed. I >> think I have also had this issues in mail-buffers where I use orgstruct >> modes. Again org-element--cache showed up. > > It means the cache is corrupted. Alas, it doesn't explain how it get > into that state. Is there a way to "reset" the cache? To get out of the bad state. >> Attached is a backtrace from yesterday where I had to stop Emacs with >> kill -usr2. The file I was working on has many tables with conjugations >> of words and some entities. > > Unfortunately, a backtrace isn't helpful in this case. I'd rather have > a relatively small Org document where the problem is guaranteed to > occur, and a bunch of commands possibly triggering it. I'm have still not found a consistent receipt to reproduce this state. . . Today I have been editing the same file without expiring issues. —Rasmus -- C is for Cookie