On 10/03/25 jman said:
> If you suspect a recent addition is causing this issue, you can bisect the
I suspected that it could be a change in my configuration. I managed to go back
and find an older config where this did not happen, so I am bisecting against
that to see what is triggering the bug.
On 10/03/25 jman said:
> If you suspect a recent addition is causing this issue, you can bisect the
> last changes by removing them one by one (with another editor) and try
> opening the file (with Emacs) until you identify the change that is causing
> the issue. A that point you can start investi
On 2025-03-11 3:06 p.m., Ihor Radchenko wrote:
Did you try sending SIGUSR2 signal?
I did, and it did not respond. Multiple C-g's made it suspend and prompt
me as to whether it should dump core, which is where I got the core file
from.
Mike
"Michael P. Soulier" writes:
> I've tried this in two custom builds of emacs 29.4 and 30.1, both on Debian
> 12.
> I've been using org-mode for a while, and using a meetings capture template
> for
> my meetings, which is really helpful.
>
> I tried to open meetings.org today and emacs burned 10
Hello,
I've tried this in two custom builds of emacs 29.4 and 30.1, both on Debian 12.
I've been using org-mode for a while, and using a meetings capture template for
my meetings, which is really helpful.
I tried to open meetings.org today and emacs burned 100% cpu and seemed to never
return. I h
"Michael P. Soulier" writes:
I tried to open meetings.org today and emacs burned 100% cpu and seemed to never
return. I had to kill it.
It's 100% reproducable in my setup. Not sure why. Any idea how to debug?
If you suspect a recent addition is causing this issue, you can bisect the last cha
