Karl Voit <devn...@karl-voit.at> writes: > My agenda generally works. However, sometimes, by working with Emacs > I get to the "status" where I can not re-generate the agenda: it is > in an endless loop with 100% of its Emacs-CPU-core. I can quit by > pressing M-g. After re-starting Emacs, it works again without > modifying my Org-files or the Emacs configuration. > > Here is a profiler CPU report after I quit the endless loop for > about a minute or so: > > ... > > Do you have any suggestion how I can check this out any further or > get rid of this behavior? >
It might be useful to M-x toggle-debug-on-error and try the agenda command again: if it gets stuck in the loop again, a C-g will produce a backtrace that might shed some light. -- Nick
