GNU bug report logs -
#67330
29.1.90.1; time-stamp slowdown in large org file after org-refile-get-targets, caused by e7b5912b23 (Improvements to long lines handling)
Previous Next
To reply to this bug, email your comments to 67330 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#67330
; Package
emacs
.
(Tue, 21 Nov 2023 14:17:05 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Yuchen Pei <id <at> ypei.org>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Tue, 21 Nov 2023 14:17:05 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Previously reported in emacs-devel at
https://lists.gnu.org/archive/html/emacs-devel/2023-06/msg00113.html
Emacs built with
./configure --with-native-compilation --with-imagemagick --with-json
Possibly related to bug#57207
Set up: foo.org is a 12MB file, longest line 4753, about 21000
headlines. It contains the timestamp thingie "Time-stamp: <....>" as one
of the first few lines that already has a timestamp from before. Say the
following file is called bar.el
#+begin_src emacs-lisp
(add-hook 'before-save-hook 'time-stamp)
(require 'org-refile)
(setq org-refile-use-cache t)
(setq org-refile-use-outline-path t)
(setq org-refile-targets '((nil :maxlevel . 5)))
(setq org-goto-interface 'outline-path-completion)
(setq large-file-warning-threshold 15000000)
(find-file "foo.org")
(org-refile-get-targets)
#+end_src
To reproduce, do
./src/emacs -Q -l bar.el foo.org
followed by eval
(time-stamp)
It will take 10+ seconds to complete, and 10+ seconds if I undo
afterwards.
Like bug#57207,
(setq long-line-threshold nil)
is a workaround, and (time-stamp) completes instantly.
I could not measure the precise time or have the whole process run in
batch mode because:
1. It does not affect batch mode, presumably because of the change has
to do with x display
2. (time-stamp) has funny pseudo-asynchronous behaviour: if I do
(progn (time-stamp) (message "Done.")) the message evals immediately,
long before time-stamp "completes" and unhangs emacs.
BTW what is the commit that fixed bug#57207? I searched for commits in
master and emacs-29 with message containing 57207 but could not find
any.
Best,
Yuchen
--
Dr Yuchen Pei | https://ypei.org | Timezone: UTC+11
PGP Key: 47F9 D050 1E11 8879 9040 4941 2126 7E93 EF86 DFD0
https://ypei.org/assets/ypei-pubkey.txt
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#67330
; Package
emacs
.
(Tue, 21 Nov 2023 14:35:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 67330 <at> debbugs.gnu.org (full text, mbox):
merge 67330 67327 67326
thanks
> From: Yuchen Pei <id <at> ypei.org>
> Date: Tue, 21 Nov 2023 23:32:23 +1100
>
> Previously reported in emacs-devel at
> https://lists.gnu.org/archive/html/emacs-devel/2023-06/msg00113.html
>
> Emacs built with
>
> ./configure --with-native-compilation --with-imagemagick --with-json
>
> Possibly related to bug#57207
You have just reported 3 exact duplicates of the same bug...
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#67330
; Package
emacs
.
(Sat, 25 Nov 2023 06:16:01 GMT)
Full text and
rfc822 format available.
Message #13 received at 67330 <at> debbugs.gnu.org (full text, mbox):
On Tue 2023-11-21 16:33:21 +0200, Eli Zaretskii wrote:
> [... 13 lines elided]
>> Possibly related to bug#57207
> You have just reported 3 exact duplicates of the same bug...
Apologies - first time reporting to debbugs, and the bug did not appear,
making me think it may have failed somehow.
Best,
Yuchen
--
Dr Yuchen Pei | https://ypei.org | Timezone: UTC+11
PGP Key: 47F9 D050 1E11 8879 9040 4941 2126 7E93 EF86 DFD0
https://ypei.org/assets/ypei-pubkey.txt
This bug report was last modified 1 year and 209 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.