emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Daniel Ortmann <daniel.ortmann@oracle.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [External] : Re: how to investigate? org-element-cache Unregistered buffer modifications detected
Date: Wed, 29 Jun 2022 13:56:23 +0800	[thread overview]
Message-ID: <87bkucko6w.fsf@localhost> (raw)
In-Reply-To: <2d1acb04-2e8d-cf3f-67e5-bc4108b268e5@oracle.com>

Daniel Ortmann <daniel.ortmann@oracle.com> writes:

> ... I rebuild at least once per day.
> My current org-mode version is:
> Org mode version 9.5.4 (release_9.5.4-596-gaa5bc2 @
> /home/dortmann/src/git-org-mode/lisp/)
>
> A bit more information may help?
>
>   * 1.2MB org-mode file
>   * received a stubborn parse error after today's build; could not load
>     my org file; the file location looked fine
>   * partitioned the large file into smaller files
>   * ... was able to load each of those smaller files
>   * afterwards, without any changes, I was able to load the full file
>     without the 'parse error'

That was related to another bug that was introduced in
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f77800c68b69f770886b9c103a101550ec530896
and then fixed in
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=d788fe99272d3563ff88e872bf337b8c198c7c7d

I now pushed another change that will prevent loading the broken
persisted cache.

>   * ... but once again received that org-element-cache warning
>   * Now, after a fresh pull of code and a rebuild, NONE of the errors or
>     warnings occur.

>
> Everything is clean now.
>
> Could loading those smaller files have cleaned or updated the cache?  Or 
> was it your code updates?

Every time you get parser error, the cache should be cleared. So, you
likely did clear the cache somewhere in the process.

In any case,
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=eb796ae4326faf246b1b1a382a0a6a372f28c9e4
should fix most of the "unregistered buffer modifications" warnings.
It will only show up in really serious cases.

Best,
Ihor


      reply	other threads:[~2022-06-29  5:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 22:21 how to investigate? org-element-cache Unregistered buffer modifications detected Daniel Ortmann
2022-06-29  2:03 ` Ihor Radchenko
2022-06-29  4:54   ` [External] : " Daniel Ortmann
2022-06-29  5:56     ` Ihor Radchenko [this message]

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.orgmode.org/

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

  git send-email \
    --in-reply-to=87bkucko6w.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=daniel.ortmann@oracle.com \
    --cc=emacs-orgmode@gnu.org \
    /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/org-mode.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).