Closed chep closed 5 years ago
Perhaps font-lock or syntax-ppss is spinning on a pathological mix of markdown and python (like what happens when we miss a close quote, and comments get parsed as code). If that were the case then turning on polymode would be the solution -- unless you already have polymode turned on. That is what I'd need to know.
Whether polymode is on or off, I'd want to see the ipynb file that reliably triggers the blowup if that could be posted here.
I have poly-ein minor mode enabled is that what you are talking about?
I can't post my notebook here sorry
If poly-ein is enabled and a minimum reproducible example cannot be furnished, then I have no further input. Sorry.
Problem description
Sometimes, while editing markdown cells, emacs freezes and uses 100% of one CPU It happens after a "long" time (maybe 15-20 minutes).
If I don't kill emacs and wait, it lasts a few minutes and then emacs is responding again.
I'm not able to stop anything with C-g so enabling debug is useless.
I compiled emacs with debug symbols and attached gdb. Emacs is always in the garbage collector functions when the problem occurs. It seems that cleaning takes very long time.
Steps to reproduce the problem
I can't reproduce the problem with emacs -Q but maybe I didn't tried enough, it's no always funny to use vanilla emacs. This could also be a problem with one of my other packages... I don't know how to debug this. If you have any idea, I can try it.
System info: