emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Alastair Burt <alastair.burt@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-persist - bug report
Date: Wed, 20 Oct 2021 20:28:29 +0800	[thread overview]
Message-ID: <87ilxrdgnm.fsf@localhost> (raw)
In-Reply-To: <CABtOJPz0cCEzuH5GGKxGuNKcGvfCkNvB-mRf2u+ZXwJng9prOA@mail.gmail.com>

Alastair Burt <alastair.burt@gmail.com> writes:

> Hi there,
> I couldn't find an issue-tracking system for org-mode as they have for
> projects on github. So I'm emailing you directly.

Thanks! The bug reporting for Org mode is by email. You can send email
to Org mailing list at emacs-orgmode@gnu.org (also, see "1.4 Feedback"
section of Org manual or https://orgmode.org/ The issue tracker is
derived from the email and can be found online in

I am CCing this message the mailing list.

> I just upgraded my org-mode to the latest version in git. Whenever I
> visited a certain org file, my Emacs became unusable. Any attempt to use
> M-x (execute-extended-command) resulted in max-specpdl-size errors as did
> using C-x C-c to exit Emacs. Some but not all of the errors mentioned
> "Error during file deserialization". After an hour's debugging, I tracked
> this down to org-persist. Deleting "~/.cache/org-persist" made the problem
> go away.

Your error looks bad, but I never saw it on my side. Are you able to
reproduce it with clean Emacs config? Does it happen immediately after
you open the file or did you change the file before the error appeared?

> I never managed to produce a backtrace, even with debug-on-error set to t.
> This was hard to debug!

This indicates some problem with cache code. The cache code is
asynchronous and thus difficult to debug. You may produce a useful
backtrace if you have

(setq org-element--cache-self-verify 'backtrace)
(setq org-element--cache-self-verify-frequency 1)

If the above is not enough, try the following just before actions that
trigger the error:

(setq org-element--cache-diagnostics t)


       reply	other threads:[~2021-10-20 12:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABtOJPz0cCEzuH5GGKxGuNKcGvfCkNvB-mRf2u+ZXwJng9prOA@mail.gmail.com>
2021-10-20 12:28 ` Ihor Radchenko [this message]
2021-10-20 14:09   ` org-persist - bug report Colin Baxter 😺
2021-10-20 14:30     ` Ihor Radchenko
2021-10-20 19:04       ` Colin Baxter 😺
2021-10-21 12:13         ` Ihor Radchenko
2021-10-21 12:25         ` Max Nikulin
2021-10-21 12:51           ` org-persist? error "Variable binding depth exceeds max-specpdl-size" (was: org-persist - bug report) Ihor Radchenko
2021-10-21 13:52           ` org-persist - bug report Colin Baxter 😺
2021-10-21 15:11             ` Ihor Radchenko
2021-10-21 15:31               ` Ihor Radchenko
2021-10-21 16:03                 ` Ihor Radchenko
2021-10-21 16:26                   ` Colin Baxter 😺
2021-10-21 16:50                   ` Max Nikulin
2021-10-21 23:31                   ` Alastair Burt

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ilxrdgnm.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=alastair.burt@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).