Stefan Monnier <[EMAIL PROTECTED]> writes: Hello Stefan,
> Does (setq jit-lock-stealth-time nil) fix it? No. If it has already started looping it has no effect at all, and if I set in in my ~/.emacs and restart it, I can reproduce the bug again, but it seems to happen not that fast. If it's set to the default of 16 I just have to open my ~/.emacs, and bam, 100% cpu utilization. If it's set to nil I had to jump arround the buffer for some time. Now I'll do what Richard suggested: Making normal backtraces and looking for a common pattern... Bye, Tassilo _______________________________________________ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
