cpu to 100% when folding org headings

[pgrond]

I have a specific org mode file, that makes the cpu spike to 100% and emacs just hangs. It only happens in this file AND with modus-themes loaded.
I am using doom emacs, and selecting a theme from the doom collection doesn't trigger the problem.

I know that this is probably not enough info to find the problem, but how do I profile this issue in emacs when emacs is totally unresponsive if the
problem occurs?

What can I do to provide more info?

[protesilaos]

On 2025-01-22 13:08, Peter Grond wrote: I have a specific org mode file, that makes the cpu spike to 100% and emacs just hangs. It only happens in this file AND with modus-themes loaded. I am using doom emacs, and selecting a theme from the doom collection doesn't trigger the problem. I know that this is probably not enough info to find the problem, but how do I profile this issue in emacs when emacs is totally unresponsive if the problem occurs? What can I do to provide more info?

Can you interrupt the lag by typing C-g? If yes, then you can try the profiler to get a report that might tell us more about what is happening. - Do M-x profiler-start - Try the folding - C-g to stop it after it hands. - M-x profiler-stop - M-x profiler-report In the resulting buffer, we will be able to see where most of the CPU is spent on.

[pgrond]

C-g does not work unfortunately.

[protesilaos]

From: Peter Grond ***@***.***> Date: Wed, 22 Jan 2025 03:36:58 -0800 C-g does not work unfortunately.

How about the ESC?

…

-- Protesilaos Stavrou https://protesilaos.com

[pgrond]

Nope, emacs still stays unresponsive, no matter what I try. pkill -SIGUSR2 -i emacs also doesn't work.
A bit more of googling points to a possible issue with font-lock (https://www.reddit.com/r/emacs/comments/ubk6kr/emacs_consuming_cpu_in_endless_loop_what_are_my/), which seems reasonable because it is theme dependent.

[protesilaos]

On 2025-01-23 12:08, Peter Grond wrote: Nope, emacs still stays unresponsive, no matter what I try. pkill -SIGUSR2 -i emacs also doesn't work. A bit more of googling points to a possible issue with font-lock (https://www.reddit.com/r/emacs/comments/ubk6kr/emacs_consuming_cpu_in_endless_loop_what_are_my/), which seems reasonable because it is theme dependent.

This is strange. The font-lock mechanism is always in effect and we are not doing anything fancy with the Org faces. Does Doom have some way to run a test in a pristine environment (with regular Emacs this is done with 'emacs -Q' at the command line)? I cannot tell what is happening in your configuration, given all the extras Doom adds.

[pgrond]

I can reproduce it with other themes too, like the ef-themes. Doom themes do not have the issue, also other basic themes like Leuven or tango doe not have the issue. I will try to narrow it down. Maybe some issue with another package/configuration.

[protesilaos]

On 2025-01-23 12:38, Peter Grond wrote: I can reproduce it with other themes too, like the ef-themes. Doom themes do not have the issue, also other basic themes like Leuven or tango doe not have the issue. I will try to narrow it down. Maybe some issue with another package/configuration.

Okay, please let me know.