"Michael P. Soulier" <msoul...@digitaltorque.ca> 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 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 investigating why that specific change. I'd probably start by profiling Emacs when opening that file.
How to profile Emacs: https://www.gnu.org/software/emacs/manual/html_node/elisp/Profiling.html Hope it helps! Cheers,
