Closed yyscamper closed 6 years ago
NCM gets its contents from various sources, Jedi bein one of those sources. In this case, it seems that Jedi itself is the problem, not NCM.
Same issue for me when I save file. And It looks like memory leak also happened.
I use vim8 in macbook pro.
Discussion moves to https://github.com/ncm2/ncm2-jedi/issues/1
I found the ncm occupy a very large CPU rate (70%-95%), the high CPU rate keeps for more than 30 minutes, and now it is still high.....
in vim windows, it stuck at
call jedi#goto_definitions